OpenClaw Gateway Won't Start

Start the diagnosis at the Gateway, not at a disconnected channel or model. The first fatal startup line usually identifies the boundary that failed.

Run the command ladder

openclaw status
openclaw gateway status
openclaw logs --follow
openclaw doctor

Match the startup signature

• Missing gateway.mode or a local-mode stamp: validate configuration and review openclaw doctor --fix.
• EADDRINUSE or another Gateway already listening: identify the existing process before starting a second copy.
• Refusal to bind without authentication: keep loopback or configure the documented authentication path.
• Permission denied: confirm that the service user owns and can access its state and workspace.
• Invalid configuration: repair the specific field; do not delete the whole state directory.

Restart only after the cause changes

openclaw gateway restart
openclaw gateway status --deep

Repeatedly restarting an unchanged fatal configuration only hides the useful first error in more log output.

Expected result

Gateway status reports Runtime: running, Connectivity probe: ok, and a capability line. Only then continue with model and channel probes.