-
-
Notifications
You must be signed in to change notification settings - Fork 69.2k
[Bug]: Web dashboard shows "disconnected (1008): unauthorized: gateway token missing" on localhost #17745
Description
Summary
On my local Mac install, the OpenClaw dashboard loads in the browser at:
http://127.0.0.1:18789/chat?session=main
but the chat panel immediately disconnects with:
disconnected (1008): unauthorized: gateway token missing (open the dashboard URL and paste the token in Control UI settings)
I never see a token prompt or a place to paste a gateway token in the Control UI, and I’m just accessing from the same machine where the gateway is running.
Environment
- Device: Mac mini 2024 M4 (headless server)
- OS: macOS (macOS 15.7.3 Sequoia)
- OpenClaw version: 2026.2.9 (33c75cb)
- Install method: curl installer on a non‑admin user account
- Gateway bind: loopback (127.0.0.1:18789)
- Auth mode during onboarding: token mode (local gateway, loopback only)
- Access method: Chrome on the same Mac, using
http://127.0.0.1:18789/chat?session=main
Steps to reproduce
- Fresh install on macOS non‑admin user:
curl -fsSL https://openclaw.ai/install.sh | bash openclaw configure # choose local gateway, loopback 127.0.0.1, token mode, etc. openclaw gateway install openclaw gateway start
On my local Mac install, the OpenClaw dashboard loads in the browser at:
http://127.0.0.1:18789/chat?session=main
Environment
- Device: Intel Mac mini (headless server)
- OS: macOS (macOS 15.7.3 Sequoia)
- OpenClaw version: 2026.2.9 (33c75cb)
- Install method: curl installer on a non‑admin user account
- Gateway bind: loopback (127.0.0.1:18789)
- Auth mode during onboarding: token mode (local gateway, loopback only)
- Access method: Chrome on the same Mac, using
http://127.0.0.1:18789/chat?session=main
Expected behavior
- On a fresh local install, opening
http://127.0.0.1:18789/from the same machine should either:- transparently authenticate the dashboard, or
- clearly prompt me once for the gateway token and then remember it.
Actual behavior
- I never see a token prompt or a place to paste a gateway token in the Control UI, and I’m just accessing from the same machine where the gateway is running.
- I seem to be stuck in a “token missing” loop with no obvious way to resolve it from the UI.
openclaw gateway statusshows gateway running and listening on 127.0.0.1:18789 (RPC probe OK).- When I open
http://127.0.0.1:18789/or/chat?session=main, the dashboard UI loads but the chat panel immediately disconnects with: - “Disconnected from gateway.”
disconnected (1008): unauthorized: gateway token missing (open the dashboard URL and paste the token in Control UI settings)(screenshot attached).- I did not manually set any
gateway.tokenor dashboard token in my config. - I never see a token prompt or a place to paste a gateway token in the Control UI, and I’m just accessing from the same machine where the gateway is running.
- I’m stuck in a “token missing” loop with no obvious way to resolve it from the UI.
OpenClaw version
2026.2.9 (33c75cb)
Operating system
macOS 15.7.3
Install method
curl installer on a non‑admin user account
Logs, screenshots, and evidence
See attached image fileImpact and severity
Affected users/systems/channels
Severity (annoying, blocks workflow, data gathering etc.)
Frequency (always)
Consequence (missed messages, unobservable data, lack of control, etc.)
Additional information
