Recover an offline server

Use this guide when Setup waits for the first check-in or reports Agent is offline. If the record is Online but a live panel fails, use live connection troubleshooting.

Check the runtime first

1. Confirm the correct runtime or agent process is running.
2. Inspect its original startup log for EnderDash loading errors.
3. Confirm the installed artifact matches that runtime, operating system, and architecture.
4. For a plugin runtime, confirm the original console recognizes enderdash.

A failed plugin load or missing native library happens before authentication. Fix that error before changing firewall ports.

Check the effective key

Open this server record's Setup page as an owner or admin. If a fresh key was generated, the installed old key no longer works.

For a command-capable runtime, register the current key:

enderdash install <agentKey>

This saves the key and reconnects without another restart. For standalone or environment-based installations, update the effective value and restart the process.

Check configuration precedence. A JVM property or environment variable can override a corrected file. Confirm the key belongs to this record and that another agent is not using it.

Check organization state

A frozen server cannot establish a new agent connection. Resolve the plan allowance before reinstalling it. Repeated key rotation does not change a plan limit.

Check signaling egress

Confirm the agent can resolve and connect to its configured signaling host over HTTPS/WebSocket. The hosted default is wss://signaling.enderdash.com/ws.

If a proxy sits in that path, confirm it supports WebSockets. If you changed signalingUrl, allow the configured host. Read network requirements for the required endpoints.

For a focused investigation, enable debugConnectionLogs, reload or restart, and inspect the relevant connection error. Sanitize logs before sharing them.

Verify registration and a live operation

1. Confirm Online in the dashboard.
2. Open Info and verify the expected runtime identity.
3. On a Paper server, open Console, send list, and find its response.
4. On a standalone host, open a supported panel and confirm fresh data.

If registration works but the live read fails, continue with browser-to-agent transport checks. Fixed WebRTC ports and manual public addresses belong to that later stage.

For help, include the runtime and agent version, installation method, time, visible state, and sanitized error in a support report.