Always show Bad Gateway error when use Foxglove in ROS1 environment

[LeZhang13]

Description
Version:1.13.2
OS:Ubantu 18.04 (Virtual Machine）
Data source (e.g. bag file, mcap file, rosbridge, ROS 1/2 native):ROS 1 native
Problem:
My ROS publisher and Foxglove all in my Virtual Machine Ubantu 18.04, I use a publisher publish the /Camea/Image, and want use Foxglove to show the web camera image by TCP/IP , but Foxglove always show error: Bad Gateway.




I don't know what problem caused.
By the way, If I change to use rosbridge, the connection is ok, Foxglove can show the web camera image.

[jtbandes]

We do recommend the rosbridge connection since it's easier to get it to work (as you have found). It also works with the web app at studio.foxglove.dev and not just the desktop app.

The error message you shared mentions a hostname of tedzhang-virtual-machine. While this doesn't show up in your printenv, this error does indicate that at least one node is reporting this hostname, so it might be in the environment (ROS_HOSTNAME) for some of your nodes (or roscore) running in different shells. It is important to ensure that each node in the system uses a hostname that can be resolved by other nodes it needs to communicate with.

Here is some ROS documentation about network setup: https://wiki.ros.org/ROS/NetworkSetup

[LeZhang13]

Hi, I export the HOSTNAME same as the error message show tedzhang-virtual-machine

But after I connect Foxglove, same error happened.


So I think this may not HOSTNAME problem. I have no idea to use native connection now.

[LeZhang13]

I change to use a local environment like win10, this issue fixed. So maybe caused by virtual environment issue.