When OpenClaw prints Gateway start blocked: set gateway.mode=local, nothing is broken. Startup is stopped on purpose because the active profile isn't set to local gateway mode.
The fix
openclaw doctor
openclaw config get gateway.mode
openclaw config set gateway.mode local
openclaw gateway status
openclaw logs --follow
config get should return local, gateway status should show the runtime as running, and the logs should stop repeating the block message.
Why it happens
- A previous profile or migration left
gateway.modeunset. - You switched environments and reused an old config.
- A remote-focused config was copied into a local setup.
If the error is still there
- If you use several profiles, make sure you changed the one that is active:
openclaw status --all, thenopenclaw config get gateway.mode. - A second blocker can show up once the mode is fixed. Look in the logs for
refusing to bind gateway ... without authorEADDRINUSEand fix those next. - After the gateway is healthy, send one real command from your chat channel to confirm it runs end to end.
The same steps, with the follow-up checks, are on the gateway.mode=local fix page. If you are installing from scratch, the install guides for macOS, Windows and Linux cover first-run checks, and the 7-day learning path walks from first install to automation.
Disclosure: I run OpenClaw Community Hub, a community site that is not affiliated with the OpenClaw project. The commands above come from the OpenClaw docs.
Which OpenClaw error cost you the most time? I'm collecting the common ones.
Top comments (0)