Why is an Explorer showing up as offline or not showing up in the console?

There are several possible reasons why the runZero Explorer might show up as offline in the web console, or not show up at all.

The first possibility is that the service might not be running. Here's how to check the task status:

• On Windows, check Windows Services for the runZero Explorer service to see if it's running. 
• On Linux, use the command systemctl status 'runzero*'
• On macOS, you can use the command launchctl list | grep runzero (as root) to check if the runzero-agent task has a PID number listed (the first number)

A common reason for the Explorer failing to run is that local EDR software has prevented it from running because the binary is unrecognized.

Another possibility is that the Explorer is running, but can't reach the runZero console. To check for this, the best option is to look at the log file. On Windows the default log file location is the installation directory (C:\Program Files\runZero) while other platforms log to the files /var/log/runzero.log and /var/log/runzero.err.

Errors such as "wss read failed: websocket: close 1006 (abnormal closure): unexpected EOF" generally indicate that the network connection is unreliable, or something is preventing the Explorer from connecting via WebSocket to the runZero cloud.

Also, note that Explorers are deployed for specific organizations, and won't show up in the deployed explorer list for other organizations.