let5see/clawdbot

Files

Peter Steinberger f76e3c1419 fix: enforce secure control ui auth

2026-01-21 23:58:42 +00:00

1.4 KiB

Raw Blame History

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

Control UI fails on HTTP (device identity required)

Service says running, but RPC probe fails

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

When filing an issue

Paste a safe report:

clawdbot status --all

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