node-connect

Diagnose and repair node-to-gateway pairing and routing failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing and repairing node-to-gateway pairing and routing failures across local networks, VPNs like Tailnet, and public URLs to ensure reliable OpenClaw connectivity.

Core Features & Use Cases

  • Canonical route verification: Confirm the node-to-gateway route (LAN, Tailnet, or public URL) is correctly advertised and usable.
  • Guided remediation: Provide concrete steps to fix pairing/auth failures, including setup-code tokens, URLs, and token refresh.
  • Robust diagnostics: Validate configurations with OpenClaw commands and status checks to prevent misrouting and regressions.

Quick Start

Launch the node-connect diagnostic to identify the active gateway route and repair pairing.

Frequently Asked Questions about node-connect

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

FAQPage Schema
Why does my node-to-gateway pairing fail with an invalid or expired bootstrap token?

Pairing failures with invalid bootstrap tokens occur when setup codes expire or are misconfigured. You must refresh the token or regenerate the setup code to repair the node-to-gateway connection.

How do I fix OpenClaw gateway remote URL pairing errors over a tailnet?

To fix remote URL pairing errors, verify the Tailscale gateway routing mode is active and confirm the publicUrl configuration is correctly advertised to resolve unauthorized connection issues.

What is the best way to diagnose local Wi-Fi working but remote gateway VPS connection issues?

Diagnosing remote VPS gateway issues requires validating the active gateway routing mode and running OpenClaw status commands to identify and repair the broken network route.

Does this diagnostic process support manual node connections when QR code setup fails?

Yes, the diagnostic process applies when QR code setup fails by guiding manual node connection steps, verifying gateway routing modes, and confirming publicUrl configurations.

How to step by step repair a gateway.bind configuration causing unauthorized pairing errors?

Repair gateway.bind unauthorized errors by verifying the active gateway routing mode, refreshing setup-code tokens, and validating the corrected publicUrl configuration through OpenClaw status checks.

When do I need to verify node-to-gateway routing modes like LAN, tailnet, or public URL?

You need to verify routing modes when local Wi-Fi works but remote gateway connections fail, or when errors indicate pairing is required, unauthorized, or experiencing bootstrap token invalidity.