node-connect

Diagnose and fix OpenClaw node-to-gateway connection and pairing failures.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Jnuso/OpenClaw --skill node-connect-jnuso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/Jnuso/OpenClaw/tree/main/skills/node-connect
Command: npx skills add https://github.com/Jnuso/OpenClaw --skill node-connect-jnuso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes the OpenClaw node connection and pairing failures, ensuring the node can reach the gateway and the app can pair reliably across devices and networks.

Core Features & Use Cases

  • Route discovery and verification: determine the actual path from node to gateway (local, VPN/Tailscale tailnet, or public URL) and confirm the gateway advertises the correct route.
  • Guided remediation: provide a step-by-step plan to re-establish pairing, validate credentials, and re-run the setup QR if needed.
  • Context-aware checks: collect environment information (gateway.bind, gateway.remote.url, pairing status) and suggest targeted fixes for both local and remote scenarios.

Quick Start

Run diagnostics to identify the real node-to-gateway route and re-establish a working pairing.

Frequently Asked Questions about node-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a node connection failure when my local Wi-Fi works but remote access is misconfigured?

A 'pairing required' or 'unauthorized' error during node setup indicates an authentication failure in your gateway connection. You must inspect the gateway.auth and bootstrap token configuration states to identify the invalid credentials and apply the recommended steps to re-establish pairing.

What is the best way to troubleshoot a bootstrap token invalid error on my gateway?

The best way to troubleshoot an invalid bootstrap token error is to run a context-aware diagnostic check on your gateway.bind and gateway.auth states. This validates your current credentials and guides you through re-running the setup QR to restore a working connection.

Does Tailscale work with gateway.remote.url for establishing node connections?

Yes, Tailscale works with gateway.remote.url by providing a VPN tailnet route for node connections. Route discovery verifies whether your node reaches the gateway locally or through the Tailscale tailnet, ensuring the gateway advertises the correct path for reliable app pairing.

How do I diagnose the actual route from my node to the gateway when QR setup fails?

To diagnose the actual route from your node to the gateway when QR setup fails, collect environment information including gateway.bind and pairing status. This route discovery process confirms whether your connection path is local or remote and guides the remediation steps.

Why does my node connection keep failing with a gateway.bind error across different networks?

A node connection fails with a gateway.bind error across networks because the gateway is not advertising the correct route to your node. You must inspect the gateway.bind configuration state to identify the binding mismatch and apply targeted fixes to re-establish a working connection.