(1008) pairing issue
Krill - Here’s a concise summary of the 1008 “pairing required” issue.
My browser has a valid device identity in openclaw-device-identity-v1 (deviceId, publicKey, privateKey, version). Nothing appears corrupted. My Control UI settings in openclaw.control.settings.v1 are also valid. I manually added a token so the UI has one available.
The problem is that the Control UI never sends the token during the WebSocket handshake. In DevTools, the WebSocket request shows no token in the URL, no Authorization header, and no cookies. The handshake is always just wss://bot.tail290504.ts.net with no authentication. Because of that, the Gateway immediately closes the connection with 1008 pairing required.
I manually tested the WebSocket connection by opening wss://bot.tail290504.ts.net?token=abc123xyz456 in the browser console. That works correctly: the Gateway accepts the connection, sends a connect.challenge event, and then closes cleanly with code 1000. This proves the token is valid and the Gateway pairing flow works when the token is included.
In the Control UI code (ui/src/ui/gateway.ts), the WebSocket is created using: this.ws = new WebSocket(this.opts.url). The token is never appended to the URL, so the Gateway never receives it. This appears to be the root cause of the pairing failure.
I also cleaned up my environment. I had a systemd service (openclaw-vite.service) that was auto-starting Vite on port 5173 and respawning Node processes. I disabled it so I can run the UI manually and ensure my code changes take effect.
Summary: The Gateway is behaving correctly and accepts the token when it’s included. The Control UI is not attaching the token to the WebSocket URL, so the Gateway always responds with 1008. I believe the fix needs to happen in the UI WebSocket constructor or wherever the token is supposed to be added.
My browser has a valid device identity in openclaw-device-identity-v1 (deviceId, publicKey, privateKey, version). Nothing appears corrupted. My Control UI settings in openclaw.control.settings.v1 are also valid. I manually added a token so the UI has one available.
The problem is that the Control UI never sends the token during the WebSocket handshake. In DevTools, the WebSocket request shows no token in the URL, no Authorization header, and no cookies. The handshake is always just wss://bot.tail290504.ts.net with no authentication. Because of that, the Gateway immediately closes the connection with 1008 pairing required.
I manually tested the WebSocket connection by opening wss://bot.tail290504.ts.net?token=abc123xyz456 in the browser console. That works correctly: the Gateway accepts the connection, sends a connect.challenge event, and then closes cleanly with code 1000. This proves the token is valid and the Gateway pairing flow works when the token is included.
In the Control UI code (ui/src/ui/gateway.ts), the WebSocket is created using: this.ws = new WebSocket(this.opts.url). The token is never appended to the URL, so the Gateway never receives it. This appears to be the root cause of the pairing failure.
I also cleaned up my environment. I had a systemd service (openclaw-vite.service) that was auto-starting Vite on port 5173 and respawning Node processes. I disabled it so I can run the UI manually and ensure my code changes take effect.
Summary: The Gateway is behaving correctly and accepts the token when it’s included. The Control UI is not attaching the token to the WebSocket URL, so the Gateway always responds with 1008. I believe the fix needs to happen in the UI WebSocket constructor or wherever the token is supposed to be added.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
