Troubleshooting
Find the guide for the symptom you can see.
Start with the observed state. An offline agent, a failed browser connection, and a missing panel need different checks.
| Symptom | Start here |
|---|---|
Plugin fails to load or the original console does not recognize enderdash | The installation guide for your runtime and its startup log |
| Setup waits for the first check-in, or the server is Offline | Recover an offline server |
| Server is Online, but live data or commands fail | Live connection troubleshooting |
| Server, Setup, or a panel is missing | Access and panel troubleshooting |
| Docker, Podman, Helm, or cluster actions are unavailable | External tools and platform access |
| Alert destination receives nothing | Alert routing and delivery checks |
| Public page is missing or shows old content | Publication troubleshooting |
| HTTP returns 401 or 403 | HTTP authentication and errors |
| Game sign-in waits forever or token exchange fails | OAuth sign-in |
| Ocelot stops or refuses an action | Ocelot troubleshooting |
Collect a useful support report
Include the runtime and agent version, installation method, approximate failure time with timezone, observed state, and the smallest operation that fails. Add the relevant sanitized startup or connection error.
Remove agent keys, API keys, OAuth secrets, cookies, tokens, webhook credentials, and personal player data from logs or screenshots.
Keep the runtime's original console or host access available during troubleshooting. Use Contact or the Discord community if the relevant guide does not resolve the symptom.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on