Recover an Offline Server

Use this guide when

Use this page when one of these is true:

• the server never reached its first successful connection
• a previously connected server is now offline
• the server connects, but direct connectivity is unreliable and relay use is frequent

Step 1: Identify the setup state

Open Downloads for the server and check which of these situations applies:

• Waiting for the first check-in: the runtime probably has not registered the key yet
• Reconnect: the server connected before, but the agent is offline now
• Reinstall: a fresh agent key is visible and still needs to be applied

If you are still on the first installation, follow Install an Agent before changing network settings.

Step 2: Fix install and key problems first

Check these items in order:

1. Confirm the correct runtime build is installed.
2. Confirm the agent actually started.
3. Confirm the agent key belongs to the same server record.
4. If the key was rotated, reinstall it and restart the runtime.

On supported runtimes, the fastest repair is usually:

enderdash install <agentKey>

Step 3: Fix restricted networking if the install is correct

If the agent is running but the browser still cannot connect reliably, apply the least invasive change that matches your environment.

Need relay-friendly connectivity on a restrictive network

Allow the hosts and ports in Network Requirements. In most restrictive environments, TURN relay support is enough to get the product working again.

Need predictable direct-connect ports

Configure a fixed WebRTC port range:

restrictPorts: true
webrtcMinPort: 10000
webrtcMaxPort: 10010

If you enable this range, forward or allow the same ports for both UDP and TCP.

Need to override the public address behind NAT

If automatic public-IP detection is blocked or wrong for your layout, advertise the public address manually:

advertisePublicAddress: true
publicAddress: "203.0.113.50"

Use the public IP that your router or edge device forwards to the runtime.

Step 4: Retry and verify

After each change:

1. Restart or reload the runtime if the config changed.
2. Refresh the server page in EnderDash.
3. Check whether the server returns to Online and whether live panels load normally.

When to use the reference pages

• Use Network Requirements when you need the exact hostnames, ports, and allowlist entries.
• Use Connection Model when you need to understand why direct connectivity, relay fallback, and public-address settings behave differently.