openclaw errors
OpenClaw error center: 429, 1008, gateway startup issues
Consolidated troubleshooting for the most common setup and runtime failures.
1. 429 rate limits
Usually caused by provider quotas or bursty concurrency.
- Check RPM quotas
- Add exponential backoff
- Queue high-volume requests
2. 1008: avoid single-cause assumptions
1008 is a policy/auth WebSocket close code and can be triggered by multiple paths.
- Missing/invalid gateway token (unauthorized)
- Unapproved pairing state (channel/device)
- Protocol/handshake mismatch (community-reported cases)
3. Triage workflow
Localize issue layer first, then isolate with minimal reproducible requests.
- Capture request IDs
- Map app and gateway logs
- Retest after each fix
Quick diagnostics commands
docker compose ps\ndocker compose logs --since=30m openclaw-gateway\ncurl -i http://127.0.0.1:18789/healthzFrequently asked questions
Why do errors return after restart?
Restart hides symptoms but not root cause. Build a config baseline and alerting.
What should I include in a support issue?
Version, logs, exact reproduction steps, and minimal config sample.