clawdbot/docs/help/troubleshooting.md

summary, read_when

summary	read_when
Troubleshooting hub: symptoms → checks → fixes	You see an error and want the fix path The installer says “success” but the CLI doesn’t work

Troubleshooting

First 60 seconds

Run these in order:

clawdbot status
clawdbot status --all
clawdbot gateway probe
clawdbot logs --follow
clawdbot doctor

If the gateway is reachable, deep probes:

clawdbot status --deep

Common “it broke” cases

clawdbot: command not found

Almost always a Node/npm PATH issue. Start here:

• Install (Node/npm PATH sanity)

Gateway “unauthorized”, can’t connect, or keeps reconnecting

• Gateway troubleshooting
• Gateway authentication

Control UI fails on HTTP (device identity required)

• Gateway troubleshooting
• Control UI

docs.clawd.bot shows an SSL error (Comcast/Xfinity)

Some Comcast/Xfinity connections block docs.clawd.bot via Xfinity Advanced Security. Disable Advanced Security or add docs.clawd.bot to the allowlist, then retry.

• Xfinity Advanced Security help: https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security
• Quick sanity checks: try a mobile hotspot or VPN to confirm it’s ISP-level filtering

Service says running, but RPC probe fails

• Gateway troubleshooting
• Background process / service

Model/auth failures (rate limit, billing, “all models failed”)

• Models
• OAuth / auth concepts

/model says model not allowed

This usually means agents.defaults.models is configured as an allowlist. When it’s non-empty, only those provider/model keys can be selected.

• Check the allowlist: clawdbot config get agents.defaults.models
• Add the model you want (or clear the allowlist) and retry /model
• Use /models to browse the allowed providers/models

When filing an issue

Paste a safe report:

clawdbot status --all

If you can, include the relevant log tail from clawdbot logs --follow.