#device signature expired

1 messages · Page 1 of 1 (latest)

elfin anvil
#

Hi folks, I’m hitting a Control UI issue after restarting Windows/WSL and would love some help.

Error shown in Web UI:
device signature expired / device signature invalid

Context:

• OpenClaw running in WSL on Windows
• After Windows reboot, I restarted OpenClaw and opened the Web UI
• Gateway is reachable, but UI disconnects with that device signature error

What I already tried:

1.Restart gateway (openclaw gateway restart)
4. Open UI again at http://127.0.0.1:18789/
5. Tried clearing site data

Still seeing the same issue.

Is this usually caused by clock skew, stale browser device identity, or something else in pairing/device auth?
Any recommended fix flow would be super appreciated 🙏

light irisBOT
#

That error is almost always clock skew between the browser and the Gateway host.

Internally the Control UI sends a device-signed handshake with a signedAt timestamp, and the Gateway rejects it if it’s more than ~2 minutes off (device signature expired). So if Windows time got corrected by NTP after boot, or WSL’s clock drifted (common after sleep/hibernate), you can get stuck in a reconnect loop and “clearing site data” won’t help.

Recommended fix flow (WSL on Windows):

  1. Check versions + logs first
  • In WSL: openclaw --version
  • In WSL (new terminal): openclaw logs --follow and watch the disconnect reason (device-signature-stale / device-signature)
  1. Verify the clocks are within 2 minutes
  • In browser devtools console: new Date().toISOString()
  • In WSL: date -Ins
    If those don’t basically match → that’s your culprit.
  1. Resync time (the pragmatic WSL fix)
  • In Windows PowerShell: wsl --shutdown