Overview

The Knowledge Base covers diagnostic of "Edge Offline" error for Edges running on customer servers via the "Docker" self installation option.

For Edges on the Xyte Secure Edge Device see Secure Edge Offline

Follow the steps below to determine the possible reason and fix it. If any of the steps fail, consult the detains in the steps on how to fix it. If all tests pass and the Edge is still not responding, please contact support at [email protected].

Troubleshooting Steps

Ping the server running the Edge to verify its running

Run ping <edge server ip>

Check the server is connected to power

Physically inspect the server to check its connected to power and powered-on.

Check Log-in to the server (all following steps to be run from within the server)

Either login locally or via remote desktop / ssh / etc.

Check outgoing network connection

Ping any local device on the network to verify outgoing connectivity:

ping <ip>

Check outgoing network connection to Xyte's server

telnet eu1.edge.xyte.io 443 (On linux/mac)

The result should be similar to:

Connected to .....eu-west-1.compute.amazonaws.com.
Escape character is '^]'.

In case of failure check if the outgoing to the internet is blocked or unavailable.

Check outbound network connectivity to eu1.edge.xyte.io from within the inner (nested) Docker container:

1. Run docker ps
2. Enter the xyte_edge container: docker exec -it xyte_edge bash
3. Run docker ps again (from inside the container, if applicable)
4. Enter the second container: docker exec -it <container_id> bash
5. Execute the command: telnet eu1.edge.xyte.io 443

Verify Docker is running

Consult your OS installation instructions to verify the Docker container is running

Linux

Mac

Windows