Explorer: "Failed to connect: no route to host"

This error generally indicates that the Explorer was prevented from reaching the runZero cloud console by a firewall.

The first thing to check is that the runZero console IP addresses can be reached by the machine hosting the Explorer. If not, the best option is to set up the firewall to allow access to those addresses.

As an alternative, if you have a proxy that will allow external access, you can configure the Explorer to use that proxy. For example:

# echo 'HTTPS_PROXY=192.0.2.17:8080' > /opt/rumble/bin/.env
# systemctl restart rumble-agent-<orgid>

(Substituting the appropriate IP address.)

Note that some proxy systems can have trouble with WebSocket connections, such as the connection the Explorer keeps open to the scheduling hub.

If you continue to experience problems, you can check the Explorer’s log files for more information. On Unix systems they are found at /var/log/rumble.log and /var/log/rumble.err.