Diagnose OpenClaw node connection and pairing failures across LAN, Tailscale, and public routes.
npx skills add https://github.com/srgaba/open-claw --skill node-connect-srgaba
Please help me install this Agent Skill. Skill: node-connect Source: https://github.com/srgaba/open-claw/tree/main/project/skills/node-connect Command: npx skills add https://github.com/srgaba/open-claw --skill node-connect-srgaba
openclaw qr --json, config getters, and openclaw devices list to read the actual advertised gatewayUrl and urlSource instead of guessing. - Root-Cause Mapping: Maps specific errors like loopback-only binding, expired bootstrap tokens, unauthorized responses, and pending pairing requests to concrete fixes. - Use Case: A user scans a QR code on the same Wi-Fi but the app cannot connect. The Skill detects the gateway is bound to loopback, recommends gateway.bind=lan, regenerates the setup code, and approves the pending device pairing. ## Quick Start Diagnose why my Android app cannot connect to my OpenClaw gateway over Tailscale and tell me the exact fix.High-intent search queries and answers about installing and using this skill.
First identify the intended route: same machine, same LAN, Tailscale tailnet, or public URL. Then run openclaw qr --json to see the actual advertised gatewayUrl and urlSource, and fix the config path that is advertising the wrong route before regenerating the setup code.
Pairing required means the network route and authentication already worked, but the device is awaiting approval. Run openclaw devices list to see the pending request, then approve it with openclaw devices approve --latest instead of changing network config.
The gateway is usually bound to loopback, so it advertises 127.0.0.1 or localhost which other devices cannot reach. Set gateway.bind=lan, restart the gateway, generate a fresh setup code, and rescan.
Yes, use gateway.tailscale.mode=serve or gateway.bind=tailnet so the gateway advertises a tailnet route. Verify the host is actually on Tailscale with tailscale status --json, and ensure gateway.auth.allowTailscale matches the intended flow.
It means the setup code is stale, often because it was generated before a URL or auth fix. Generate a fresh setup code after correcting the route configuration and rescan it in the app.
abhiunixDiagnose OpenClaw node connection and pairing failures across local, tailnet, and public paths.
brikkoAIDiagnose Brikko Studio node-to-gateway connection and pairing failures across network topologies.
wangqianCAIDiagnose network connectivity, authentication, and pairing failures between OpenClaw nodes and gateways.
vut08905Diagnose and repair node-to-gateway pairing and routing failures.