pairing issues killed 3 days - help
β
Solved
I've been bouncing between perplexity, gemini and the cli installation process for 3 days - initially fo rtelegram pairing - which i gave up on and moved to whats app. And now after finally restarting and trying to enable Brave for web search - i have a whole new (or maybe old) pairing issue. Whatsapp kindly compiled this for me, Any help appreciated. I am a sliver away from giving up entirely !!! β β―Subject: Persistent "pairing required" error preventing sub-agent spawning
Hello OpenClaw Support Team,
I'm encountering a persistent "gateway closed (1008): pairing required" error whenever my agent attempts to spawn a sub-agent. This issue has prevented me from utilizing sub-agents for critical tasks like job searching.
Here's what I've observed and the troubleshooting steps I've taken:
Problem Description:
My agent consistently receives the error
My Setup:
* Operating System: Linux 6.8.0-90-generic (x64)
* Node.js Version: 22.22.0
* OpenClaw Version: 2026.2.19-2
* Gateway Target: ws://127.0.0.1:18789 (local loopback)
Diagnostic Outputs & Observations:
1.
β―β
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-20.log
Command: /usr/bin/node /home/johnbroaders/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
(continues next message)
Hello OpenClaw Support Team,
I'm encountering a persistent "gateway closed (1008): pairing required" error whenever my agent attempts to spawn a sub-agent. This issue has prevented me from utilizing sub-agents for critical tasks like job searching.
Here's what I've observed and the troubleshooting steps I've taken:
Problem Description:
My agent consistently receives the error
gateway closed (1008): pairing requiredsessions_spawnopenclaw status --deepMy Setup:
* Operating System: Linux 6.8.0-90-generic (x64)
* Node.js Version: 22.22.0
* OpenClaw Version: 2026.2.19-2
* Gateway Target: ws://127.0.0.1:18789 (local loopback)
Diagnostic Outputs & Observations:
1.
openclaw gateway statusβ―β
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-20.log
Command: /usr/bin/node /home/johnbroaders/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
(continues next message)
Solution
Thatβs super usefulβthanks for circling back with the actual fix.
Iβll treat this as a confirmed workaround: if
If this fixed it for you, please right-click the solution message β Apps β
Mark Solution so Answer Overflow indexes it for the next person.
Iβll treat this as a confirmed workaround: if
gateway closed (1008): pairing requiredsudo rebootsessions_spawnIf this fixed it for you, please right-click the solution message β Apps β
Mark Solution so Answer Overflow indexes it for the next person.
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?
