node-connect

Diagnose OpenClaw node connection and pairing failures across companion apps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix 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

  • Comprehensive diagnostics for node connectivity and device pairing across major mobile and desktop companions.
  • Guidance across routing scenarios (same machine, same LAN, Tailnet, public URL) with actionable remediation steps.
  • Clear, CLI-guided remediation to verify gateway status and apply fixes without exposing sensitive data.

Quick Start

Provide observed symptoms and let the system guide you through diagnosing and fixing the OpenClaw node connection.

Frequently Asked Questions about node-connect

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

FAQPage Schema
How do I fix OpenClaw node connection and pairing failures on iOS or Android?

Fix OpenClaw node connection failures by diagnosing routing scenarios and validating gateway status. Use CLI commands like qr, devices list, and gateway status to identify incorrect routing or invalid setup codes and apply targeted remediation steps.

Why does my OpenClaw companion app work on local Wi-Fi but fail to connect over VPS or Tailnet?

OpenClaw companion apps fail over VPS or Tailnet due to incorrect gateway routing or Tailscale configuration. Diagnose the connection by checking gateway.remote.url settings and verifying gateway status to ensure proper remote URL binding.

What does the bootstrap token invalid or expired error mean during OpenClaw device pairing?

The bootstrap token invalid or expired error means the OpenClaw device pairing token is no longer valid. Resolve this by regenerating the QR or setup code and validating the plugins.entries.device-pair.config.publicUrl configuration.

How do I troubleshoot gateway.bind errors when connecting an OpenClaw node?

Troubleshoot gateway.bind errors by checking the OpenClaw gateway status and verifying the gateway.remote.url configuration. Use CLI diagnostics to determine correct routing across local, Tailnet, or public URL environments and apply fixes.

Can I diagnose OpenClaw pairing issues on macOS using the command line?

Yes, you can diagnose macOS OpenClaw pairing issues using command line tools. Run OpenClaw commands such as qr, devices list, and gateway status to validate routing, check for unauthorized errors, and apply remediation without exposing sensitive data.

What should I do if OpenClaw returns a pairing required or unauthorized error?

A pairing required or unauthorized error indicates failed OpenClaw node authentication. Validate your setup code or QR pairing method, check the publicUrl configuration, and use gateway status commands to verify correct device routing and authorization.