Stuck in "Pairing Required" loop β CLI not showing requests [Windows/Docker]
Title: Stuck in "Pairing Required" loop on Windows/Docker
The Issue:
I'm stuck in a Disconnected (1008): pairing required loop on the Gateway UI. Despite multiple attempts, I cannot get the "Green" online status.
Environment:
β’ OS: Windows 10/11 (PowerShell)
β’ OpenClaw Version: 2026.2.6-3 (Docker)
β’ Access: http://127.0.0.1:18789 with token secret123.
What I've tried:
1. Pairing CLI: Clicking "Connect" in the UI then immediately running pairing list --channel telegram returns No pending telegram pairing requests.
2. System Password: Added OPENCLAW_SYSTEM_PASSWORD=admin123 to docker-compose.yml. Entered it in the UI, but it still demands pairing.
3. Manual Bypass Attempt: Tried setting dmPolicy="open" and allowFrom=["*"].
β’ Result: Hit a PowerShell syntax error: Config validation failed: channels.telegram.allowFrom: Invalid input: expected array, received string. PowerShell seems to strip the brackets/quotes, preventing the JSON array from being recognized.
4. Networking: Switched from localhost to 127.0.0.1 and updated the gateway command to --bind 0.0.0.0.
Gateway Logs:
[ws] closed before connect conn=... code=1008 reason=pairing required
Question:
How can I bypass this pairing requirement on Windows when the CLI won't catch the browser's request? Is there a way to manually authorize the session ID or a specific syntax for allowFrom that works in PowerShell?
The Issue:
I'm stuck in a Disconnected (1008): pairing required loop on the Gateway UI. Despite multiple attempts, I cannot get the "Green" online status.
Environment:
β’ OS: Windows 10/11 (PowerShell)
β’ OpenClaw Version: 2026.2.6-3 (Docker)
β’ Access: http://127.0.0.1:18789 with token secret123.
What I've tried:
1. Pairing CLI: Clicking "Connect" in the UI then immediately running pairing list --channel telegram returns No pending telegram pairing requests.
2. System Password: Added OPENCLAW_SYSTEM_PASSWORD=admin123 to docker-compose.yml. Entered it in the UI, but it still demands pairing.
3. Manual Bypass Attempt: Tried setting dmPolicy="open" and allowFrom=["*"].
β’ Result: Hit a PowerShell syntax error: Config validation failed: channels.telegram.allowFrom: Invalid input: expected array, received string. PowerShell seems to strip the brackets/quotes, preventing the JSON array from being recognized.
4. Networking: Switched from localhost to 127.0.0.1 and updated the gateway command to --bind 0.0.0.0.
Gateway Logs:
[ws] closed before connect conn=... code=1008 reason=pairing required
Question:
How can I bypass this pairing requirement on Windows when the CLI won't catch the browser's request? Is there a way to manually authorize the session ID or a specific syntax for allowFrom that works in PowerShell?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
