Troubleshooting | OpenClaw

Help Center 3 sections

Troubleshooting

This page is for situations where something is already broken. You do not need every concept first. Run the checks in order, then branch based on the symptom you actually see.

Help Center FAQ Gateway Deep Troubleshooting

The First Sixty Seconds

Run in this order

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

Add this after the Gateway responds

When configured is not the same as healthy, go deeper.

openclaw status --deep

Common Symptoms -> Direction

PATH

openclaw: command not found

This is usually a Node or npm PATH problem. Verify where Node is installed, reopen the terminal or reinstall the CLI.

Installer

The installer failed or got stuck

Re-run the install path with verbose output so you can see the full error instead of guessing.

Gateway unauthorized / endless reconnects

This usually comes from token, URL, remote mode or insecure HTTP context issues. Continue from Gateway troubleshooting.

Models

Model failure / all models failed

Check openclaw models status first, then confirm the current agent actually has auth for that provider.

Service

The service looks alive but nothing responds

Read gateway status, gateway probe and live logs together to distinguish a loaded supervisor entry from a working Gateway listener.

Docs

Docs pages or SSL access look broken

If you see ISP filtering or SSL errors, switch networks, use a mobile hotspot or VPN and verify whether the problem is your local network policy.

Before Reporting an Issue

Prefer to include the output of openclaw status --all. It is usually safe enough to paste and contains the context most first-line debugging needs.

If you can add the relevant tail from openclaw logs --follow, diagnosis becomes much faster.

If config is part of the suspicion, do not paste raw tokens directly. Confirm they are redacted first.