Adapted community discussion: Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from August 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.
I cannot get into the Control UI on the local WebSocket address. Even when openclaw dashboard opens the page directly, it keeps telling me the server updated and reloads again. Hard refresh does not clear it.
The dashboard is reaching the Gateway, but the browser UI bundle and Gateway may be out of sync. This does not look like the usual bad-token screen.
Please run openclaw --version and share the exact text under the expanded raw error. Keep the dashboard URL and token private. A hard reload is also safe to try. If the message changes to pairing required, inspect the newest request with openclaw devices list.
The CLI reports OpenClaw 2026.8.1-beta.2.
The raw error points to stale Control UI state, not authentication. Close every dashboard tab, clear site data only for the dashboard origin, unregister its service worker, and reopen a fresh link from openclaw dashboard.
If it still loops, run openclaw gateway status --deep and share the sanitized output along with the browser name and whether a reverse proxy or Tailscale sits between the browser and Gateway.
Deep status says the registered Windows service is stopped, yet the local port is listening and a terminal client is connected.
That suggests a manually started or stale Gateway process is serving the port instead of the registered service. Close any terminal running a foreground Gateway, then run:
openclaw gateway restart
openclaw gateway status --deep
Once status shows a running service and healthy connectivity, reopen a fresh dashboard link. Because this Gateway is loopback-only, test on the same Windows machine and do not expose the port publicly just to troubleshoot it.
The sanitized Gateway log shows the Control UI connection is rejected because the browser build and Gateway build have different timestamps, even though the displayed version is the same.
That log is decisive. It is not a Brave-specific problem. The browser UI and Gateway came from different compiled artifacts, so the Gateway rejects the WebSocket after authentication. Refreshing cannot reconcile two different builds.
Install one clean, supported OpenClaw package, then make the managed service use that same installation. Do not copy individual build folders between releases, and do not delete your OpenClaw state directory. On the current CLI, the service switch is:
openclaw gateway install --force
openclaw gateway restart
openclaw gateway status --deep
Then reopen the Control UI from a fresh openclaw dashboard link.