solution gateway high linux macos windows

Gateway won't start: 'refusing to bind ... without auth'

Fix gateway startup failures when binding to LAN/tailnet without token/password auth configured.

By CoClaw Team •

Symptoms

  • Gateway immediately exits and logs show:
    • refusing to bind gateway to <host>:18789 without auth (...)
  • openclaw gateway status shows the service restarting/crashing.

Cause

When the gateway binds to a non-loopback interface (LAN/tailnet/custom), OpenClaw requires auth to be configured before it listens on that network path. Treat the exact token/password config shape as version-specific and confirm it against the current gateway auth/configuration guide for your installed version.

Fix

1) Set gateway auth through the current config guide

Use token or password auth as documented for your installed version:

Then restart the gateway. Do not disable auth or expose a naked LAN/tailnet dashboard just to make the bind succeed.

2) Or bind only to loopback (local-only)

If you do not need LAN access, bind to loopback (127.0.0.1) and use SSH tunnel / local access.

Verify

  • openclaw gateway status shows running.
  • Use openclaw dashboard for a fresh tokenized browser entrypoint when auth is required.
  • The Control UI stays connected on the intended loopback/tunnel/LAN route.

Verification & references

  • Reviewed by:CoClaw Code Team
  • Last reviewed:March 14, 2026
  • Verified on: Linux · macOS · Windows

References

Official docs

  1. OpenClaw docs: /gateway/authentication
  2. OpenClaw docs: /gateway/troubleshooting
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

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.
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'.
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: CLI/UI is probing the wrong machine (local vs remote mode mismatch)
Fix
Fix confusing 'gateway unreachable' states by aligning gateway.mode, gateway.remote.url, profiles/state dirs, and the URL you probe.
OpenClaw Configuration Guide: openclaw.json, Models, Gateway, Channels, and Plugins
Guide
Set up openclaw.json without guesswork: confirm the active config path, choose a safe baseline, add providers and channels in the right order, and verify each change before it becomes a production problem.
OpenClaw Control UI Auth & Pairing: Fix 'unauthorized', 1008, and Remote Dashboard Access
Guide
Restore stable Control UI access by separating gateway auth from device pairing, fixing unauthorized and 1008 loops, and verifying that your remote path stays stable.