Operations: Troubleshooting
This page is the troubleshooting index for ClawControl operators.Common Incident Areas
- startup failures
- port conflicts
- OpenClaw missing/unavailable
- gateway auth-required responses
- workspace validation failures
- loopback policy violations
- unsigned desktop launch friction
First-response Checks
- Confirm local listeners are loopback only.
- Confirm database path and migration state.
- Check both dependency layers:
- gateway reachability in settings/topbar
- CLI availability/version in settings
- Confirm OpenClaw CLI exists on PATH (or
OPENCLAW_BINis set). - Re-run gateway test from setup/settings flow.
- Refresh capabilities (
/api/openclaw/capabilities?refresh=1) and retry. - Check activity/receipt logs for failed operations.
Targeted Guides
- Startup Failures and Port Conflicts
- OpenClaw/Auth/Workspace Errors
- Loopback Policy Violations
- Unsigned Desktop Install
- Release Distribution + Checksums