Fix “OpenClaw Gateway not running” or “not reachable”

Decision order

1. 1

   Read status

   Record service owner, config path, endpoint, port, and probe result.

   openclaw gateway status --json

   Copy
2. 2

   Validate config

   Resolve invalid mode, port, bind, auth, or plugin config before restart loops.

   openclaw config validate --json
   openclaw doctor --json

   Copy
3. 3

   Require RPC

   Confirm the expected Gateway responds beyond a bare listener.

   openclaw gateway status --require-rpc

   Copy
4. 4

   Inspect logs

   Use the resolved log path or bounded follow output; redact before sharing.

   openclaw logs --follow

   Copy

Only then change service state

• If no managed service exists, decide whether to install one or run the Gateway in the foreground.
• If a different process owns the port, stop and identify it rather than killing processes by name.
• If the endpoint is remote, verify URL, TLS, tunnel/private-network path, and explicit credentials.
• Use `openclaw gateway restart --safe` when the current version supports a safe restart handoff and the service owner is known.