Fix · gateway · auth

OpenClaw (Moltbot) gateway auth failed (401 / unauthorized)

If tools can’t invoke the gateway, this is usually a token mismatch or a bind/surface issue.

Fast checks

# Is the gateway running?
openclaw gateway status

# Follow logs and reproduce the auth error
openclaw logs --follow

Most common causes

  • Wrong token: your client/tool is using an old gateway token after you rotated it.
  • Bind mode: if you bound beyond loopback, you should require auth and restrict access.
  • Reverse proxy: proxy can strip headers or change perceived source IP.

Fix checklist

1
Restart gateway after config changes
openclaw gateway restart
2
Re-pair / re-auth your client
If your setup uses a stored token, update it and retry.
3
Verify your bind/proxy settings
If you changed bind/proxy rules, re-check which ports are internet-facing, and ensure auth is required.
Back to error index →

Rename note: “OpenClaw (Moltbot)” is used for SEO continuity during the rename.