31 replies

unintended multiple gateway installs

✅Solved

Hi Krill - as the title says, I think I accidentally installed multiple gateway services. Here's the output of openclaw doctor --fix:

OpenClaw doctor

Other gateway-like services detected

- mission-control.service (user, unit: /home/deploy/.config/systemd/user/mission-control.service)

Cleanup hints

- systemctl --user disable --now openclaw-gateway.service
- rm ~/.config/systemd/user/openclaw-gateway.service

Gateway recommendation

Recommendation: run a single gateway per machine for most setups.
One gateway supports multiple agents.
If you need multiple gateways (e.g., a rescue bot on the same host), isolate ports + config/state (see docs: /gateway#multiple-gateways-same-host).

Security

- No channel security warnings detected.
- Run: openclaw security audit --deep

Skills status

Eligible: 14
Missing requirements: 37
Blocked by allowlist: 0

Plugins

Loaded: 4
Disabled: 27
Errors: 0

Gateway

Gateway not running.

Gateway connection

Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/deploy/.openclaw/openclaw.json
Bind: loopback

Gateway

Runtime: stopped (state activating, sub auto-restart, last exit 1, reason 1)
Service is loaded but not running (likely exited immediately).
File logs: /tmp/openclaw/openclaw-2026-02-09.log
Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager

Restarted systemd service: openclaw-gateway.service
Updated ~/.openclaw/openclaw.json
Backup: ~/.openclaw/openclaw.json.bak

Doctor complete.

Solution

Found it — it’s not “multiple gateways”, it’s just the service crashing because the unit is using an old bind syntax:

Invalid --bind (use "loopback", "lan", "tailnet", "auto", or "custom")
ExecStart ... --bind 0.0.0.0

Invalid --bind (use "loopback", "lan", "tailnet", "auto", or "custom")
ExecStart ... --bind 0.0.0.0

In current OpenClaw,

--bind

--bind

no longer takes an IP.

0.0.0.0

0.0.0.0

is now:

-

--bind lan

--bind lan

(binds to

0.0.0.0

0.0.0.0

, all interfaces)
- or

--bind loopback

--bind loopback

(localhost only, safest default)

Fix (minimal change, keep your env vars)

1) Stop the crash loop:

systemctl --user stop openclaw-gateway.service

systemctl --user stop openclaw-gateway.service

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2d ago•

31 replies

.\boba

unintended multiple gateway installs

✅Solved

Solution

Found it — it’s not “multiple gateways”, it’s just the service crashing because the unit is using an old bind syntax:

Invalid --bind (use "loopback", "lan", "tailnet", "auto", or "custom")
ExecStart ... --bind 0.0.0.0

Invalid --bind (use "loopback", "lan", "tailnet", "auto", or "custom")
ExecStart ... --bind 0.0.0.0

In current OpenClaw,

--bind

--bind

no longer takes an IP.

0.0.0.0

0.0.0.0

is now:

-

--bind lan

--bind lan

(binds to

0.0.0.0

0.0.0.0

, all interfaces)
- or

--bind loopback

--bind loopback

(localhost only, safest default)

Fix (minimal change, keep your env vars)

1) Stop the crash loop:

systemctl --user stop openclaw-gateway.service

systemctl --user stop openclaw-gateway.service

Jump to solution

unintended multiple gateway installs

Fix (minimal change, keep your env vars)

unintended multiple gateway installs

Fix (minimal change, keep your env vars)

Similar Threads

Similar Threads

Similar Threads