solution gateway high linux

Linux: gateway doesn't stay running (systemd service not installed)

If the gateway only runs in the foreground or stops after you close SSH, install/repair the systemd service and enable user lingering.

By CoClaw Team •

Symptoms

  • The gateway works while the terminal is open, but stops when you exit (or after SSH disconnects).
  • systemctl --user status openclaw-gateway.service says the unit does not exist.
  • openclaw gateway status shows not running after reboot.

Cause

The gateway is running in the foreground, but the systemd (user) service was not installed/enabled (or it points at an old OpenClaw install path).

Fix

1) Install (or reinstall) the gateway service

On the gateway host:

openclaw gateway install

If you recently switched install methods (npm ↔ git) or profiles, force a rewrite:

openclaw gateway install --force

2) Check the service status

systemctl --user status openclaw-gateway.service

Restart if needed:

systemctl --user restart openclaw-gateway.service

Enable systemd user lingering:

loginctl enable-linger "$USER"

Verify

  • openclaw gateway status shows running.
  • After logging out and back in (or after reboot), the gateway is still running.

Verification & references

  • Reviewed by:CoClaw Editorial Team
  • Last reviewed:March 14, 2026
  • Verified on: Linux
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

Linux/systemd: OpenClaw leaves orphan gateway processes or port 18789 conflicts
Fix
Fix Linux hosts where CLI-triggered gateway respawn collides with a systemd-managed OpenClaw gateway, causing orphan processes, EADDRINUSE, or 'another gateway instance is already listening'.
Windows (WSL2): gateway service install fails (systemd not enabled)
Fix
Fix WSL2 gateway daemon install issues by enabling systemd in /etc/wsl.conf, shutting down WSL, and retrying openclaw gateway install.
Gateway: service says running but the CLI/UI can't connect (probe fails)
Fix
Fix 'running but unreachable' gateway states by checking you're probing the right URL, confirming the port is listening, and aligning auth/bind settings.
Gateway fails to start: EADDRINUSE / another gateway instance is already listening
Fix
Fix OpenClaw gateway port conflicts (EADDRINUSE) by stopping the other process or choosing a new gateway port/profile.
OpenClaw Installation Troubleshooting: Node/NPM, PATH, Windows (WSL2), and Docker
Guide
A layered checklist for the most common 'can't install' / 'command not found' / 'service won't start' failures. Covers Node version, global install permissions, PATH issues, WSL2 systemd, and Docker setup gotchas.
OpenClaw Configuration Guide: openclaw.json, Models, Gateway, Channels, and Plugins
Guide
A beginner-friendly but thorough guide to OpenClaw configuration: where openclaw.json lives, safe defaults, model/provider setup, gateway auth/networking, channels, plugins, and the most common config pitfalls.