An "explorer timeout" occurs when the runZero hub hasn't received any updates from the Explorer in an extended period of time — for example, if the network connection has been down for over an hour, or if DNS has failed.
Typically the Explorer logs will show it repeatedly attempting to reconnect:
time="2023-10-17T17:39:31-05:00" level=info msg="connecting to hub at wss://console.runzero.com/socket/explorer/connect directly"
time="2023-10-17T17:39:31-05:00" level=error msg="failed to connect to wss://console.runzero.com/socket/explorer/connect: dial tcp: lookup console.runzero.com: no such host"
time="2023-10-17T17:39:31-05:00" level=error msg="failed to connect: dial tcp: lookup console.runzero.com: no such host"
Or:
time="2023-10-21T13:42:33-05:00" level=info msg="connecting to hub at wss://console.runzero.com/socket/explorer/connect directly"
time="2023-10-21T13:42:34-05:00" level=info msg="registering with hub at wss://console.runzero.com/socket/explorer/connect"
time="2023-10-21T13:42:34-05:00" level=info msg="registering with organization ID 4448576d-2777-4999-a111-39ed5d8afbbb"
time="2023-10-21T13:42:34-05:00" level=info msg="waiting for the registration response..."
time="2023-10-21T15:28:34-05:00" level=error msg="failed to register with wss://console.runzero.com/socket/explorer/connect: read tcp 192.168.0.222:55675->76.223.34.198:443: i/o timeout"
time="2023-10-21T15:28:34-05:00" level=error msg="failed to connect: read tcp 192.168.0.222:55675->76.223.34.198:443: i/o timeout"
Information on where to find the logs is at https://www.runzero.com/docs/installing-an-explorer/#log-management
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article