Duplicate Gateway Service?
✅Solved
I'm running the gateway in a debian 13 LXC running on Proxmox 9. I'm running it as user hunter (not root) but I notice this "Other gateway-like services detected" when running openclaw gateway status. Can you help me debug what's going on?
hunter@clawd:~$ openclaw gateway status
OpenClaw 2026.2.9 (33c75cb) — If it works, it's automation; if it breaks, it's a "learning opportunity."
│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-11.log
Command: /usr/bin/node /home/hunter/.local/share/pnpm/global/5/.pnpm/openclaw@2026.2.9@napi-rs+canvas@0.1.91@types+express@5.0.6_node-llama-cpp@3.15.1_signal-polyfill@0.2.2/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://192.168.1.52:18789
Dashboard: http://192.168.1.52:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 192.168.1.52.
Runtime: running (pid 12402, state active, sub running, last exit 0, reason 0)
RPC probe: ok
Listening: *:18789
Other gateway-like services detected (best effort):
- openclaw-node.service (user, unit: /home/hunter/.config/systemd/user/openclaw-node.service)
Cleanup hint: systemctl --user disable --now openclaw-gateway.service
Cleanup hint: rm ~/.config/systemd/user/openclaw-gateway.service
Recommendation: run a single gateway per machine for most setups. One gateway supports multiple agents (see docs: /gateway#multiple-gateways-same-host).
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).
hunter@clawd:~$ openclaw gateway status
OpenClaw 2026.2.9 (33c75cb) — If it works, it's automation; if it breaks, it's a "learning opportunity."│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-11.log
Command: /usr/bin/node /home/hunter/.local/share/pnpm/global/5/.pnpm/openclaw@2026.2.9@napi-rs+canvas@0.1.91@types+express@5.0.6_node-llama-cpp@3.15.1_signal-polyfill@0.2.2/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://192.168.1.52:18789
Dashboard: http://192.168.1.52:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 192.168.1.52.
Runtime: running (pid 12402, state active, sub running, last exit 0, reason 0)
RPC probe: ok
Listening: *:18789
Other gateway-like services detected (best effort):
- openclaw-node.service (user, unit: /home/hunter/.config/systemd/user/openclaw-node.service)
Cleanup hint: systemctl --user disable --now openclaw-gateway.service
Cleanup hint: rm ~/.config/systemd/user/openclaw-gateway.service
Recommendation: run a single gateway per machine for most setups. One gateway supports multiple agents (see docs: /gateway#multiple-gateways-same-host).
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).
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
