node-connect

Diagnose and resolve OpenClaw node pairing failures across Android, iOS, and macOS.

1.0k|59|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill node-connect-safeai-lab-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/SafeAI-Lab-X/ClawKeeper/tree/main/legacy/clawkeeper-watcher/skills/node-connect
Command: npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill node-connect-safeai-lab-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes OpenClaw node connection and pairing failures across Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Core Features & Use Cases

  • Diagnose and resolve connectivity and pairing issues between OpenClaw agents and gateways across platforms (Android, iOS, macOS).
  • Provide clear remediation steps and checks to determine whether the routing, authentication, or configuration is misaligned.
  • Real-world use: when a user cannot establish pairing via QR, this skill helps identify whether the issue is network routing, tailscale reachability, or gateway URL misconfig.

Quick Start

Run the node-connect skill to diagnose and fix OpenClaw node pairing failures.

Frequently Asked Questions about node-connect

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

FAQPage Schema
Why does OpenClaw node pairing fail when local Wi-Fi works but VPS or tailnet does not?

OpenClaw node pairing fails over VPS or tailnet when the gateway URL is misconfigured or Tailscale reachability is blocked. This skill diagnoses those routing mismatches across Android, iOS, and macOS to restore valid gateway connections.

How do I fix an invalid or expired bootstrap token error in OpenClaw?

To fix an invalid or expired bootstrap token, you must re-establish a valid gateway pairing. This skill guides you through canonical openclaw checks and remediation steps to resolve unauthorized pairing errors and refresh tokens.

What causes a 'pairing required' or unauthorized error during OpenClaw QR setup?

A 'pairing required' or unauthorized error during QR setup usually indicates a misalignment in network routing, Tailscale reachability, or the gateway URL. This skill identifies whether the failure stems from authentication or configuration issues.

How do I troubleshoot gateway.remote.url or gateway.bind errors in OpenClaw?

Troubleshooting gateway.remote.url or gateway.bind errors involves checking network routing and gateway configurations. This skill provides guided remediation steps to correct misaligned settings and re-establish a valid gateway pairing.

Does this OpenClaw troubleshooting process work across Android, iOS, and macOS companion apps?

Yes, the OpenClaw troubleshooting process diagnoses and resolves node connection failures across Android, iOS, and macOS companion apps. It applies canonical checks to fix QR code failures and gateway pairing issues on all supported platforms.

What should I do when plugins.entries.device-pair.config.publicUrl causes a connection failure?

When the publicUrl configuration causes a connection failure, you need to verify your gateway and Tailscale settings. This skill enforces canonical openclaw commands to diagnose and remediate the misconfigured publicUrl property.