Files
openclaw/docs/help/troubleshooting.md
2026-02-06 10:00:08 -05:00

2.6 KiB
Raw Blame History

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

Troubleshooting

First 60 seconds

Run these in order:

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

If the gateway is reachable, deep probes:

openclaw status --deep

Common “it broke” cases

openclaw: 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://openclaw.ai/install.sh | bash -s -- --verbose

For beta installs:

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --beta --verbose

You can also set OPENCLAW_VERBOSE=1 instead of the flag.

Gateway “unauthorized”, cant connect, or keeps reconnecting

Control UI fails on HTTP (device identity required)

docs.openclaw.ai shows an SSL error (Comcast/Xfinity)

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

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 its non-empty, only those provider/model keys can be selected.

  • Check the allowlist: openclaw 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:

openclaw status --all

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