edgegap-troubleshoot

原文涵盖的主题

• 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

这里只展示节选，请以完整原文和当前要求为准。