control ui requires device identity: OpenClaw dashboard fixes
OpenClaw's dashboard refused with 1008: control ui requires device identity, device identity required, or origin not allowed. What each means and the fix.
Both refusals come from the Gateway checking the browser before it lets the dashboard connect. “Control ui requires device identity (use HTTPS or localhost secure context)” means the page arrived without a signed device key. Since OpenClaw 2026.8.1 the dashboard makes that key over plain HTTP too, so the fix is updating OpenClaw. origin not allowed means the address in your browser bar is not one the Gateway accepts: add it to gateway.controlUi.allowedOrigins or set gateway.publicOrigin. The clean ways in from another machine are an SSH tunnel to 127.0.0.1:18789 or Tailscale Serve over HTTPS.
Which message you have
All of these close the dashboard’s connection with code 1008, so the dashboard shows them after disconnected (1008):. As OpenClaw 2026.11.6 prints them:
control ui requires device identity (use HTTPS or localhost secure context)
device identity required
origin not allowed (use gateway.publicOrigin with allowedOrigins omitted, or allow this origin in gateway.controlUi.allowedOrigins)Copied- “Control UI requires device identity”: the dashboard connected without a device identity. Sent only to the Control UI.
- “Device identity required”: the same refusal for any other client, such as a third-party dashboard or a script on the Gateway’s WebSocket. The troubleshooting page reads it as “the client did not provide the identity required by its role and auth policy.” The fix is on that client’s side.
- “Origin not allowed”: the page’s origin failed the Gateway’s browser-origin check. A close reason is capped at 120 bytes, so this one can arrive cut off at
gateway.controlUi.allo. Releases from early 2026 worded it “origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)”.
A Gateway token does not stand in for the device key. OpenClaw’s docs say it plainly: in token or password mode, “the Control UI still requires browser device identity.”
“Requires device identity”: an older dashboard
The browser proves which device it is by signing with a key it makes and keeps. Browsers only give a page their built-in cryptography on HTTPS or localhost, so on a plain http://<server-ip>:18789 page an older dashboard could not make the key, and the Gateway refused it. OpenClaw 2026.8.1 (August 31, 2026) shipped “Restore Control UI device pairing on plain HTTP”, which does the signing in the page’s own code. The current docs now say that opening the dashboard over plain HTTP, on a LAN or Tailscale address, works.
So the fix is updating OpenClaw on the server: the Gateway serves the dashboard, so a current Gateway means a current dashboard. If the Gateway is already current, the tab may be holding an older copy of the page; the troubleshooting page names browser cache and stale tab state as the usual leftovers, and a fresh load clears them.
Two settings from older answers do not help. Error text from early 2026 suggested gateway.controlUi.allowInsecureAuth: true for token-only HTTP; users on 2026.2.21 reported it still ended in 1008, and current docs no longer document it. gateway.controlUi.dangerouslyDisableDeviceAuth, once the break-glass switch that turned device checks off, is now a “retired break-glass input, now fully inert” per the security docs, and openclaw doctor --fix removes it. There is “no persistent config switch that disables device identity.”
“Origin not allowed”: tell the Gateway its address
The Gateway accepts a browser page without any configuration when the address in the bar is the Gateway’s own and is private: localhost, a private or Tailscale IP, or a name ending in .local or .ts.net. Everything else needs an entry: a server’s public IP, a domain name, a reverse proxy, a tunnel service that forwards a public port. The Gateway configuration offers two ways:
{
gateway: {
// the HTTPS address the Gateway is reached at; it becomes the allowlist
publicOrigin: "https://gateway.example.com",
controlUi: {
// or an explicit list, which replaces publicOrigin's default
// allowedOrigins: ["https://control.example.com"],
},
},
}CopiedAn origin is scheme, host and port, exactly as the browser shows it. An explicit list, even an empty one, replaces the publicOrigin default. ["*"] is accepted on current releases (it did not help a reporter on 2026.2.28), and the docs say to avoid it outside tightly controlled local testing, as they do for dangerouslyAllowHostHeaderOriginFallback.
If the address you were typing is http://<public-ip>:18789, the refusal is the smaller problem: the Gateway is reachable from the internet over plain HTTP, where the token travels readable. The docs call HTTP “a LAN-only convenience”, and a Gateway on a public interface is the setup to undo rather than allowlist.
The ways in from another machine
An SSH tunnel. From your own computer, with the Gateway left on loopback (the remote access docs):
ssh -N -L 18789:127.0.0.1:18789 user@gateway-hostCopiedThen open http://127.0.0.1:18789/ in your browser. Localhost passes the origin check and counts as a secure context. The same pattern for any server app is in opening a localhost app on a remote server.
Tailscale Serve. The route OpenClaw’s Tailscale docs set up: HTTPS from your own devices, with the Gateway still on loopback. Run openclaw gateway --tailscale serve, or set it in config:
{
gateway: {
bind: "loopback",
tailscale: { mode: "serve" },
},
}CopiedThen open https://<magicdns>/. Serve needs HTTPS turned on for your tailnet.
An HTTPS reverse proxy. Put its address in gateway.publicOrigin. With gateway.auth.mode: "trusted-proxy", an identity-aware proxy signs you in, and it is the one documented case where an operator’s dashboard can connect without a device key, when the browser cannot supply one.
What comes next: pairing
Getting past these checks usually brings one more message the first time a browser connects: disconnected (1008): pairing required. That is the device key working. Approve the browser with openclaw devices list and openclaw devices approve <requestId> on the server, or open the dashboard with openclaw dashboard, which the docs call the preferred path: a short-lived, single-use pairing link. A new browser profile, or cleared site data, pairs again. The scope version of that message, on a browser that was already paired, is in fixing “pairing required”, and the dashboard guide covers what the Control UI is for.