Before filing a new topic, please provide the following information.
Core DAppNode Packages versions
- bind.dnp.dappnode.eth: 0.2.13
- core.dnp.dappnode.eth: 0.3.21
- dappmanager.dnp.dappnode.eth: 0.2.123, commit: bd39b21a
- https.dnp.dappnode.eth: 0.2.2
- ipfs.dnp.dappnode.eth: 0.2.27
- notifications.dnp.dappnode.eth: 0.1.9
- premium.dnp.dappnode.eth: 0.1.1
- vpn.dnp.dappnode.eth:
- wifi.dnp.dappnode.eth: 0.2.11
- wireguard.dnp.dappnode.eth: 0.1.4
System info
- dockerComposeVersion: 5.0.0
- dockerServerVersion: 29.1.2
- dockerCliVersion: 29.1.2
- os: debian
- versionCodename: bookworm
- architecture: amd64
- kernel: 6.1.0-39-amd64
- Disk usage: 90%
Openclaw doesn’t work remotely.
It gives “device identity required” error:
device identity required
This page is HTTP, so the browser blocks device identity. Use HTTPS (Tailscale Serve) or open http://127.0.0.1:18789 on the gateway host.
If you must stay on HTTP, set gateway.controlUi.allowInsecureAuth: true (token-only).
Docs: Tailscale Serve · Docs: Insecure HTTP
But gateway.controlUi.allowInsecureAuth is set to true in config.
This is the same issue as in here ([Bug]: `dangerouslyDisableDeviceAuth: true` ignored in 2026.3.11 — Control UI rejects HTTP connections with "device identity required" · Issue #44485 · openclaw/openclaw · GitHub). But on the dappnode version it hasn’t been fixed yet!
Dappnode openclaw is basically not usable remotely.