'Fix "Gateway start blocked: set gateway.mode=local"'

When OpenClaw prints Gateway start blocked: set gateway.mode=local, the gateway is not broken; startup is intentionally stopped because the active profile is not set to local gateway mode.

The direct fix is openclaw config set gateway.mode local, followed by openclaw gateway status to confirm the local gateway is running. This page gives you the shortest fix path, profile checks, and validation checklist for exact gateway error queries.

What This Error Means

OpenClaw expected local gateway mode, but your active config is unset or set to another mode.

Typical causes:

• A previous profile or migration left gateway.mode unset.
• You switched environments and reused an old config.
• A remote-focused config was copied into a local runtime.

Quick Fix

Run these commands in order:

openclaw doctor
openclaw config get gateway.mode
openclaw config set gateway.mode local
openclaw gateway status
openclaw logs --follow

Expected outcome:

• openclaw config get gateway.mode returns local.
• openclaw gateway status shows runtime is running.
• openclaw logs --follow no longer repeats the startup block error.

If the Error Still Appears

1) Confirm active profile and config scope

If you use multiple profiles, make sure you are updating the one currently in use.

openclaw status --all
openclaw config get gateway.mode

2) Check auth/bind constraints

A second blocker may appear after fixing gateway mode, such as binding without auth.

Look for logs like:

• refusing to bind gateway ... without auth
• EADDRINUSE

For these, continue with:

• Gateway troubleshooting
• Gateway health checks

3) Validate end-to-end command flow

After startup is healthy, run one real command from your channel to confirm execution.

If channel messages do not flow, check:

• Channels troubleshooting
• CLI logging

Related Guides

• CLI logs —follow guide
• General troubleshooting
• Getting started