OpenClaw Device Token Mismatch Issue after Update (v2026.2.21-2)
Dear OpenClaw Support Team,
I am writing to report a persistent "device_token_mismatch" error that occurred after updating my OpenClaw installation to version 2026.2.21-2. This issue is preventing the proper functioning of the browser control service and the OpenClaw Gateway Dashboard.
Here's a summary of the steps I've taken and the current situation:
Initial Problem: After updating OpenClaw to version 2026.2.21-2, I encountered "device_token_mismatch" errors in the gateway logs, preventing the browser tool from connecting.
Troubleshooting Steps Attempted:
Renamed /home/user/.openclaw/devices/paired.json to paired.json.bak.
Restarted the OpenClaw gateway using openclaw gateway restart.
Attempted to re-onboard using openclaw onboard. This command presented an interactive prompt requiring "y" input and a browser authorization step. Despite confirming "Yes" and attempting browser authorization, the issue persists.
Checked openclaw status, which indicates the Gateway service is "running (pid 44820, state active)".
Navigated to the OpenClaw Gateway Dashboard (http://127.0.0.1:18789/). The dashboard consistently shows "Health OFFLINE" and "disconnected (1008): unauthorized: device token mismatch".
Tried refreshing the "Devices" section in the "Nodes" page of the dashboard, but no paired devices appear.
Re-attached/detached the Chrome extension several times.
Current Status: The "device_token_mismatch" error is still present, and neither the browser control service nor the Gateway Dashboard can establish a healthy connection. The browser relay extension is reachable, but tabs cannot be attached for control.
This issue is critical as it prevents me from utilizing essential browser automation features.
Could you please provide guidance or a solution to fully resolve this device token mismatch and restore proper browser functionality?
Thank you for your time and assistance.
Sincerely,
beck99119911
I am writing to report a persistent "device_token_mismatch" error that occurred after updating my OpenClaw installation to version 2026.2.21-2. This issue is preventing the proper functioning of the browser control service and the OpenClaw Gateway Dashboard.
Here's a summary of the steps I've taken and the current situation:
Initial Problem: After updating OpenClaw to version 2026.2.21-2, I encountered "device_token_mismatch" errors in the gateway logs, preventing the browser tool from connecting.
Troubleshooting Steps Attempted:
Renamed /home/user/.openclaw/devices/paired.json to paired.json.bak.
Restarted the OpenClaw gateway using openclaw gateway restart.
Attempted to re-onboard using openclaw onboard. This command presented an interactive prompt requiring "y" input and a browser authorization step. Despite confirming "Yes" and attempting browser authorization, the issue persists.
Checked openclaw status, which indicates the Gateway service is "running (pid 44820, state active)".
Navigated to the OpenClaw Gateway Dashboard (http://127.0.0.1:18789/). The dashboard consistently shows "Health OFFLINE" and "disconnected (1008): unauthorized: device token mismatch".
Tried refreshing the "Devices" section in the "Nodes" page of the dashboard, but no paired devices appear.
Re-attached/detached the Chrome extension several times.
Current Status: The "device_token_mismatch" error is still present, and neither the browser control service nor the Gateway Dashboard can establish a healthy connection. The browser relay extension is reachable, but tabs cannot be attached for control.
This issue is critical as it prevents me from utilizing essential browser automation features.
Could you please provide guidance or a solution to fully resolve this device token mismatch and restore proper browser functionality?
Thank you for your time and assistance.
Sincerely,
beck99119911
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
