edgegap-troubleshoot
Diagnose why a game server on Edgegap will not start, keeps restarting, stops early, or cannot be reached, for any engine: image push and pull failures (401, 403, 424 "unable to pull image"), exec format errors, 422 couldn't allocate, Error deployments, crash loops and OOM kills, 100% CPU, deployments stopping after 60 minutes or 24 hours, missing logs, clients timing out or failing to connect (internal vs external port, protocol, 0.0.0.0 binding, wss and TLS Upgrade), and matchmaker players stuck searching. Use when someone says their Edgegap deployment, server or matchmaking "isn't working", or pastes an Edgegap error. Unity-specific build and SDK issues are in edgegap-unity.
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Troubleshooting an Edgegap deployment
- 1. Image and registry
- 2. App version and deploy request
- 3. Server process
- 4. Clients can't connect
- 5. Matchmaker
- When to escalate
Find the layer that failed, get evidence from it, then fix the root cause. Layers, in order: build → image → registry → app version → deployment → server process → network → matchmaker. Don't change two layers at once. Evidence first, with the edgegap MCP tools when connected (rules: the edgegap skill's references/agent-rules.md): edgegaplistappversions, edgegapgetdeployment, edgegapgetdeploymentlogs (container logs plus crash data: exit code, OOM, restart count), edgegaplistdeployments. Read logs before stopping anything: they are deleted when a deployment stops, unless Endpoint Storage is configured. For crashes that are hard to catch live, suggest keeping logs: edgegaplistendpointstorage shows whether a bucket exists, and edgegapupdateappversion with endpointstorage exports each deployment's logs there when it ends. Without tools, the dashboard deployment page shows the same. Also check https://status.edgegap.com before deep debugging. | Symptom | Cause / fix | |---|---| | push 401 Unauthorized | Not logged in to the registry (docker login registry.edgegap.com -u ' '). Retrying doesn't help | | push 403 Forbidden / denied | Logged in as a user without push rights, to the wrong r
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- edgegap/llm-agent-skills
- Source file
- skills/edgegap-troubleshoot/SKILL.md
- Fixed revision
- fd510ba826ea29ab359e70e185d2e650ef6827de
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: edgegap/llm-agent-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T08:01:42.950Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.