Make openclaw dashboard accessible from all device | Friends of the Crustacean 🦞🤝 | Page 1

spice sail Apr 18, 2026, 1:54 PM

#

Right now i can only access the openclaw dashboard from my pc im running it on.
Can can i access from other devices on the same network?

fervent etherBOT Apr 18, 2026, 1:54 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

hearty gardenBOT Apr 18, 2026, 1:54 PM

#

native depotBOT Apr 18, 2026, 1:56 PM

#

Yep, but for the dashboard I’d recommend Tailscale Serve over raw LAN access.

Best option

If you want LAN-only access

set gateway.bind: "lan" (not 0.0.0.0)
keep gateway auth enabled (token or password)
set gateway.controlUi.allowedOrigins to the exact origin you’ll open, for example:

{
  gateway: {
    bind: "lan",
    auth: { mode: "token", token: "replace-me" },

#

    controlUi: {
      allowedOrigins: ["http://192.168.1.50:18789"],
    },
  },
}

Gotchas

new browser/device needs one-time approval: openclaw devices list then openclaw devices approve <requestId>
plain LAN HTTP is a non-secure browser context, so dashboard access from another device can hit device-auth/security issues. HTTPS via Tailscale or a reverse proxy is the cleaner fix.

Docs:

#

Paste openclaw --version and whether you installed via Docker or native, and I can give you the exact commands.

spice sail Apr 18, 2026, 2:31 PM

#

Why is it giving this error when trying to log in:
control ui requires device identity (use HTTPS or localhost secure context)

native depotBOT Apr 18, 2026, 2:32 PM

#

That error usually means you’re opening the dashboard over plain LAN HTTP, like http://192.168.x.x:18789/.

Why it happens:

So:

Fixes

Best: use Tailscale Serve
openclaw gateway --tailscale serve
then open https://<magicdns>/
Or: put OpenClaw behind an HTTPS reverse proxy

#Make openclaw dashboard accessible from all device