Troubleshooting
Fast checks and common fixes for OpenClaw setup and runtime issues
First 60 seconds
Start with these commands to get signal quickly:
openclaw status openclaw status --all openclaw gateway probe openclaw logs --follow openclaw doctor
If the problem persists, run a deeper probe:
openclaw status --deep
Common cases
More common cases coming soon.
The openclaw command is not found
This is usually a PATH or install issue. Start here:
If it still fails, re-run the installer and ensure your shell loads the updated PATH.
Installer fails
Re-run installer with verbose logs:
curl -fsSL https://openclaw.ai/install.sh | bash -s -- --verbose
For beta builds:
curl -fsSL https://openclaw.ai/install.sh | bash -s -- --beta --verbose
When reporting issues, include the --verbose output.
If you’re behind a proxy or TLS interception, try a different network and re-run with verbose logs.
Dashboard says unauthorized
Use the tokenized dashboard URL (or trusted Tailscale identity headers) to satisfy auth.
Web UI won’t load
Confirm the gateway is reachable and the port/bind mode matches your network.
Can’t access docs.openclaw.ai (SSL error)
If you see ERR_CERT_DATE_INVALID, verify your system time and TLS inspection settings.
If you see NET::ERR_CERT_AUTHORITY_INVALID, your network may be intercepting TLS.
- Try a different network (mobile hotspot).
- Disable corporate TLS inspection or install the proper root CA.
If it still fails, include the full browser error and OS/network details.
RPC probe fails
Confirm the daemon is running and the RPC endpoint is reachable.
Model/provider auth fails
Model is not allowed
If you see Model … is not allowed, the gateway policy is blocking it.
Update your config to allow the model or switch to an allowed one.
- Check your configured default model in models.default.
- Verify provider availability in openclaw models status.
- If using subscription OAuth, ensure the correct profile is selected.
If unsure, paste sanitized <code>openclaw models status</code> output.
Filing an issue
When asking for help, include a reproducible summary and these outputs:
openclaw status --all
Attach openclaw status --all (tokens are redacted) and a short relevant log tail.