openclaw - 💡(How to fix) Fix Dashboard: 'pairing required' on fresh install — token not passed through WebSocket connect [1 participants]

Multiple connection attempts all fail identically — cause: pairing-required, reason: not-paired. The requestId stays constant across retries suggesting the UI reuses the same request.

Fix Plan

The issue is caused by the missing token in the WebSocket connect frame. To fix this, we need to modify the client-side code to include the token in the WebSocket connection.

Code Changes

We need to modify the WebSocket connection establishment code to include the token from the URL fragment. Here's an example:

// Get the token from the URL fragment
const urlParams = new URLSearchParams(window.location.hash.slice(1));
const token = urlParams.get('token');

// Establish the WebSocket connection with the token
const ws = new WebSocket(`ws://127.0.0.1:18789/?token=${token}`);

Alternatively, you can use the Authorization header to pass the token:

// Get the token from the URL fragment
const urlParams = new URLSearchParams(window.location.hash.slice(1));
const token = urlParams.get('token');

// Establish the WebSocket connection with the token in the Authorization header
const ws = new WebSocket(`ws://127.0.0.1:18789/`);
ws.headers = {
  'Authorization': `Bearer ${token}`
};

Verification

To verify the fix, restart the gateway and dashboard, and check the gateway logs for successful WebSocket connections. The dashboard should now connect and show the control UI without requiring pairing.

Extra Tips

• Make sure to handle token expiration and renewal properly to avoid connection issues.
• Consider using a more secure method to pass the token, such as using a secure cookie or a token exchange mechanism.