#Gateway wont start

1 messages Β· Page 1 of 1 (latest)

sly karma
#

Gateway start blocked: existing config β”‚
β”‚ is missing gateway.mode. Treat this as suspicious or clobbered config. Re-run openclaw β”‚ β”‚ onboard --mode local or openclaw setup, set gateway.mode=local manually, or pass β”‚
β”‚ --allow-unconfigured.

But I ran openclaw setup and got the error stayed

cosmic dewBOT
manic isleBOT
#

openclaw setup is supposed to write gateway.mode=local, so if the error stayed, my guess is one of two things:

  1. gateway is reading a different config file than setup wrote, or
  2. you're on an older version with a config-write bug.

Can you paste the output of these 3 commands first?

openclaw --version
openclaw config file
openclaw config get gateway.mode

If gateway.mode comes back empty/unset, force it manually:

sly karma
#

openclaw --version
openclaw config file
openclaw config get gateway.mode
OpenClaw 2026.4.14 (323493f)

🦞 OpenClaw 2026.4.14 (323493f) β€” iMessage green bubble energy, but for everyone.

~/.openclaw/openclaw.json

🦞 OpenClaw 2026.4.14 (323493f) β€” Your second brain, except this one actually remembers where you left things.

local

manic isleBOT
#

Nice, that helps a lot.

Since openclaw config get gateway.mode already says local, the problem is probably not the current CLI config. The next likely culprit is service/profile drift, meaning the background Gateway is reading a stale config or different state dir.

Can you run these and paste the output?

openclaw gateway status --deep
openclaw config validate

Also, which exact command is failing?

openclaw gateway
# or
#
openclaw gateway run
# or
openclaw gateway start

That distinction matters:

  • If openclaw gateway works, but openclaw gateway start fails, it is almost certainly the managed service metadata.
  • If both fail, I want to see what status --deep says about the config path/service path.

If status --deep shows the CLI config and service config disagree, the docs-recommended repair is:

openclaw gateway install --force
openclaw gateway restart