# Revision history [back]

started roslaunch server http://192.168.1.5 :39884/


How did you set your ROS_IP? There is most likely a space between the 5 and :39884. As this is then used to form the command passed to SSH, we get

env ROS_MASTER_URI=http://192.168.1.32:11311 ~/ch-bot_ws/devel/env.sh roslaunch -c 192.168.1.32-0 -u http://192.168.1.5 :39884/ [..]


notice the space here again. The :39884/ is then interpreted as the launch file positional argument to roslaunch (as it's no longer part of the -u argument).

Also: env-loader="~/ch-bot_ws/devel/env.sh": it's recommended to use absolute paths only for env-loader scripts, as ~ would resolve to the home dir of the remote user, which requires you to mirror the exact same folder layout on your remote system. If you use absolute paths, the script could be anywhere.