Gateway returns "pairing required" after update to 2026.2.19-2Just updated to 2026.2.19-2 (45d9b20
✅Solved
• openclaw gateway status → shows Runtime: running, RPC probe: ok, port 18789 listening on loopback
• openclaw health → fails with "pairing required"
• openclaw doctor → says "Gateway not running" even though process is alive (pid confirmed)
• openclaw status → shows gateway as "reachable 64ms" with "auth token" present
• Config: gateway.auth.mode = "token" with a 48-char token, gateway.mode = "local", bind = "loopback"
• Tried: gateway stop + start, gateway install, doctor --fix, killing all gateway processes and restarting — same error every time
• OS: Linux 6.8.0-94-generic (x64), Node 22.22.0
• 6 agents configured, 51 sessions, Telegram + Slack channels working fine before update
Inter-agent sessions_send also fails with the same "pairing required" error. Everything was working before the update.
• openclaw health → fails with "pairing required"
• openclaw doctor → says "Gateway not running" even though process is alive (pid confirmed)
• openclaw status → shows gateway as "reachable 64ms" with "auth token" present
• Config: gateway.auth.mode = "token" with a 48-char token, gateway.mode = "local", bind = "loopback"
• Tried: gateway stop + start, gateway install, doctor --fix, killing all gateway processes and restarting — same error every time
• OS: Linux 6.8.0-94-generic (x64), Node 22.22.0
• 6 agents configured, 51 sessions, Telegram + Slack channels working fine before update
Inter-agent sessions_send also fails with the same "pairing required" error. Everything was working before the update.
Solution
--verbosegateway.remote.urlOPENCLAW_GATEWAY_URL2) If you’re on the gateway host, force a loopback WS URL (auto-approved)
Try:If you see a pending request, approve it:
Then retry:
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
Was this page helpful?
