OpenClaw Control UI Cannot Connect

Fix a blank dashboard, failed WebSocket, authentication loop, pairing request, or unreachable local Control UI.

Symptom

The Control UI does not load, stays disconnected, closes with WebSocket code 1008, or repeatedly asks for authentication or pairing.

Last verified

August 9, 2026

Reviewed against

OpenClaw 2026.7.1-2 documentation

Difficulty

Intermediate

Time

~8 minutes

Verified against the official documentation listed below

The HTML page and its Gateway WebSocket use the same base address. Determine whether the failure happens before the page loads, during Gateway authentication, or during device pairing.

Check the local owner path

On the Gateway host:

openclaw gateway status
openclaw dashboard
openclaw logs --follow

The default local URL is http://127.0.0.1:18789/. If that works but a LAN or remote URL does not, fix the tunnel, private route, HTTPS, firewall, or advertised address instead of changing the local Gateway.

Repair authentication

Gateway auth runs before pairing. Generate a persistent token if needed:

openclaw doctor --generate-gateway-token
openclaw gateway auth-token --show

Paste it into the current browser session. Repeated wrong credentials can trigger a temporary auth lockout; wait for the retry time after correcting the token.

Approve the current device

openclaw devices list
openclaw devices approve <requestId>

Use a persistent browser profile. Private browsing and cleared site data create a new device identity.

Expected result

The local page loads.
WebSocket authentication succeeds.
The current browser is approved once.
A new chat remains connected.

Source notes

Technical facts on this page were checked against primary sources.

OpenClaw Control UI OpenClaw remote access