Troubleshooting

The Dock does not come online

• Check Docker is running: docker version should show a server version.
• In the Dock's folder, docker compose exec dock /app/dock status shows whether it is enrolled and linked to Sleevecast.
• The Dock needs outbound HTTPS to connect.sleevecast.com, api.sleevecast.com, auth.sleevecast.com and ghcr.io. A proxy that blocks WebSockets on 443 stops the link.
• On a machine without IPv6, the first connection attempt can fail and the next one, about five seconds later, succeeds. That is normal.

A sleeve shows Flatlined

The Fleet shows the error the Dock reported. Common causes:

• The model key is missing or rejected on that Dock. The Keys page shows each key's state per Dock; seal it again or check it with your provider.
• The model name is wrong for the provider. Fix conscience.model, save, and apply the new version.
• Not enough memory on the machine for the limits in the spec.

A sleeve shows Degraded

A new version failed to start and the previous one keeps running. Apply the previous version, or fix the spec and apply again.

A sleeve shows Unresponsive

The container runs but the sleeve stopped reporting during a task. Halt it, or resleeve it: its memory stays.

Guarded

A task hit one of the spec's guards. The Fleet and the Events page name the guard. Usually a sleeve answers before its token budget runs out; when it trips anyway, check its ready event for how many tokens its tool definitions add to every turn, and keep only the tools it needs (tools on each MCP server). Otherwise raise the guard in the spec, or give smaller tasks.

Converse never answers

• Answers can take minutes for long tasks; the console waits up to 30 minutes.
• A long task already running can delay the answer to a new message.
• If the Dock went offline, the answer is lost: send the message again when it is back.

Still stuck

Beta testers can reply to their invitation email with the Dock's status output and what they tried.