2.5 KiB
2.5 KiB
summary, read_when
| summary | read_when | ||
|---|---|---|---|
| Troubleshooting hub: symptoms → checks → fixes |
|
Troubleshooting
First 60 seconds
Run these in order:
moltbot status
moltbot status --all
moltbot gateway probe
moltbot logs --follow
moltbot doctor
If the gateway is reachable, deep probes:
moltbot status --deep
Common “it broke” cases
moltbot: command not found
Almost always a Node/npm PATH issue. Start here:
Installer fails (or you need full logs)
Re-run the installer in verbose mode to see the full trace and npm output:
curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose
For beta installs:
curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose
You can also set CLAWDBOT_VERBOSE=1 instead of the flag.
Gateway “unauthorized”, can’t connect, or keeps reconnecting
Control UI fails on HTTP (device identity required)
docs.molt.bot shows an SSL error (Comcast/Xfinity)
Some Comcast/Xfinity connections block docs.molt.bot via Xfinity Advanced Security.
Disable Advanced Security or add docs.molt.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
Model/auth failures (rate limit, billing, “all models failed”)
/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:
moltbot config get agents.defaults.models - Add the model you want (or clear the allowlist) and retry
/model - Use
/modelsto browse the allowed providers/models
When filing an issue
Paste a safe report:
moltbot status --all
If you can, include the relevant log tail from moltbot logs --follow.