"pairing required" loop
✅Solved
System: Linux (x64) | OpenClaw v2026.2.19-2 | Node v25.5.0
Architecture: Local Loopback (Gateway & Node on same machine: 127.0.0.1)
The Critical Error:
The local Browser Node cannot connect to the Gateway. The connection is immediately rejected by the Gateway during the WebSocket handshake.
Error Log (Repeated):
node host gateway closed (1008): pairing required
gateway connect failed: Error: pairing required
What We Have Tried (and Failed):
1. Disabled Auth in Config: Edited ~/.openclaw/openclaw.json to set gateway.auth.mode = "none" (replacing the previous token mode). The Gateway ignores this and still demands pairing.
2. Manual Token Injection: Attempted to run the node process manually passing the known operator token: OPENCLAW_GATEWAY_TOKEN=... openclaw node run .... Result: Same error (1008 pairing required).
3. Process Kill & Restart: Hard killed (kill -9) the Gateway process and restarted it. Result: Persistence of the error implies state/config caching or a mismatch between the CLI client and the daemon.
4. Systemd Restart: Restarted the openclaw-node.service. It enters a restart loop (Start -> Connect Fail 1008 -> Crash -> Retry).
Hypothesis:
The OpenClaw Gateway is stuck in a "Safe Mode" or "Pairing Mode" where it refuses any connection (even from localhost with auth: none) until a specific handshake or "approval" command is issued from a trusted client. The devices/paired.json file exists, but the Node is likely being treated as a new, untrusted device rather than a recognized component.
The Ask for the AI:
"How do I force the OpenClaw Gateway to accept the local Node connection immediately? Is there a CLI command to manually approve the localhost node, or a specific file in ~/.openclaw/ I need to delete to reset the pairing state fully?"
Architecture: Local Loopback (Gateway & Node on same machine: 127.0.0.1)
The Critical Error:
The local Browser Node cannot connect to the Gateway. The connection is immediately rejected by the Gateway during the WebSocket handshake.
Error Log (Repeated):
node host gateway closed (1008): pairing required
gateway connect failed: Error: pairing required
What We Have Tried (and Failed):
1. Disabled Auth in Config: Edited ~/.openclaw/openclaw.json to set gateway.auth.mode = "none" (replacing the previous token mode). The Gateway ignores this and still demands pairing.
2. Manual Token Injection: Attempted to run the node process manually passing the known operator token: OPENCLAW_GATEWAY_TOKEN=... openclaw node run .... Result: Same error (1008 pairing required).
3. Process Kill & Restart: Hard killed (kill -9) the Gateway process and restarted it. Result: Persistence of the error implies state/config caching or a mismatch between the CLI client and the daemon.
4. Systemd Restart: Restarted the openclaw-node.service. It enters a restart loop (Start -> Connect Fail 1008 -> Crash -> Retry).
Hypothesis:
The OpenClaw Gateway is stuck in a "Safe Mode" or "Pairing Mode" where it refuses any connection (even from localhost with auth: none) until a specific handshake or "approval" command is issued from a trusted client. The devices/paired.json file exists, but the Node is likely being treated as a new, untrusted device rather than a recognized component.
The Ask for the AI:
"How do I force the OpenClaw Gateway to accept the local Node connection immediately? Is there a CLI command to manually approve the localhost node, or a specific file in ~/.openclaw/ I need to delete to reset the pairing state fully?"
Solution
(1008): pairing requiredgateway.auth.*127.0.0.1role: nodeFix (headless / systemd friendly)
1) Trigger a fresh pairing request (start the node host once, or let the service try once).2) On the gateway host, approve the pending device:
3) Verify it’s now paired/connected:
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
Was this page helpful?
