OpenClaw gateway.loopback_no_auth: What It Means and How to Fix It

Published 2026-10-22 · Updated 2026-10-22 · By The Is My Agent Safe team

Short answer

gateway.loopback_no_auth is a finding from openclaw security audit. OpenClaw's docs rate it critical. Follow the fix steps below, then run openclaw security audit --deep again and check that the finding no longer appears.

This page covers one finding from OpenClaw's own security audit: what it means, how to fix it, and what to check afterward. It's based on OpenClaw's docs and source, linked at the end.

Paste your audit: run openclaw security audit --deep and paste the output into our free check for a red/amber/green result with the most important finding first (Limits of the check).

How to fix it

  1. Check your current auth settings with openclaw config get gateway.auth.
  2. This stops your agent. It stays offline until you start it again a few steps below. Stop the Gateway with openclaw gateway stop before you change anything. Make a backup with openclaw backup create, and a quick copy of your config file so you can undo the change (openclaw config file shows where it is).
  3. Set gateway.auth.mode to token and generate a token with openclaw doctor --generate-gateway-token. Changing the auth mode needs a Gateway restart.
  4. If a reverse proxy on this machine forwards to the Gateway, set gateway.trustedProxies to that proxy's address and leave gateway.allowRealIpFallback at false (the default). That covers the two related checkIds below.
  5. Start the Gateway and reconnect the Control UI and other clients with the new token. If the Control UI was reachable through a proxy or tunnel without auth, follow the full rollback plan in OpenClaw's exposure runbook, and OpenClaw's full incident-response plan if you think someone used it.
openclaw config get gateway.auth
openclaw gateway stop
openclaw backup create
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak  # use the path from openclaw config file if it's different
openclaw config set gateway.auth.mode token
openclaw doctor --generate-gateway-token
# only if a reverse proxy forwards to the Gateway (use your proxy's address):
openclaw config set gateway.trustedProxies '["PROXY_IP"]' --strict-json
openclaw config set gateway.allowRealIpFallback false
openclaw config validate
openclaw gateway start
openclaw security audit --deep

After any change, run openclaw config validate. If you stopped the Gateway, start it with openclaw gateway start. Then run openclaw security audit --deep and check that the finding is gone.

OpenClaw's docs say openclaw security audit --fix doesn't fix this finding, so the steps above are manual.

What this finding means

OpenClaw's audit raises this, as critical, when the Gateway listens only on loopback (this machine), the Control UI is on, and no Gateway auth is set up: no token or password, no trusted-proxy auth, and no Tailscale Serve identity. Loopback stops other machines from connecting directly. The finding's own text names the risk: if the Control UI is reached through a reverse proxy, "unauthenticated access is possible". OpenClaw's docs say Gateway auth is required by default and onboarding creates a token even for loopback. When OpenClaw's maintainers declined to hide the no-auth startup warning on loopback (#91151), they said loopback "does not make an unauthenticated gateway risk-free".

checkIdRating in OpenClaw's docsWhat OpenClaw's docs say it flags
gateway.loopback_no_authcriticalReverse-proxied loopback may become unauthenticated
gateway.trusted_proxies_missingwarnReverse-proxy headers are present but not trusted
gateway.real_ip_fallback_enabledwarn/criticalTrusting X-Real-IP fallback can enable source-IP spoofing via proxy misconfig

What it looks like in the audit output

Made-up example, not from a real agent:

CRITICAL gateway.loopback_no_auth
Gateway auth missing on loopback
gateway.bind is loopback but no gateway auth secret is configured. If the Control UI is exposed through a reverse proxy, unauthenticated access is possible.
Fix: Set gateway.auth (token recommended) or keep the Control UI local-only.

WARN gateway.trusted_proxies_missing
Reverse proxy headers are not trusted

False alarms and open reports

What our free check covers

The free check at /check is paste-only. We check the text you paste: your openclaw security audit output. The check never connects to your agent or tests anything live. Nothing is installed into the agent you're checking. Green means no issues found in the checks we ran. The free check puts the most important finding first, in plain English, with how to fix that one when we have steps for it. The full report explains every finding and lists the fixes in order. The check doesn't detect malicious skills. We don't review the code inside skills or MCP servers ourselves, beyond what OpenClaw's own audit reports. The check is free, and a full report is $29. See Limits of the check.

Next steps

Sources

  1. OpenClaw docs: security audit checks (checkId catalog)
  2. OpenClaw docs: openclaw backup
  3. OpenClaw docs: openclaw config (config file)
  4. OpenClaw 2026.10.5 source: src/security/audit-gateway-config.ts (where the check is defined)
  5. OpenClaw docs: network exposure (Gateway auth, reverse proxies)
  6. OpenClaw docs: Gateway configuration (auth modes, trustedProxies, allowRealIpFallback)
  7. OpenClaw docs: trusted proxy auth
  8. OpenClaw docs: config hot reload (auth mode changes need a restart)
  9. OpenClaw docs: Gateway service commands (start, stop)
  10. OpenClaw docs: openclaw security (audit suppressions)
  11. OpenClaw GitHub issue #91151: auth mode=none startup warning on loopback (closed, not planned)
  12. OpenClaw GitHub issue #70357: trusted_proxies_missing severity on loopback (closed)
  13. OpenClaw GitHub issue #17447: acknowledging audit findings (open)
  14. OpenClaw docs: exposure runbook (full rollback plan)
  15. OpenClaw docs: operator incident response (full plan)