node-connect

Diagnose RX01 node connection and pairing failures across Android, iOS, and macOS apps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RJB07/RX01 --skill node-connect-rjb07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/RJB07/RX01/tree/main/core/skills/node-connect
Command: npx skills add https://github.com/RJB07/RX01 --skill node-connect-rjb07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose RX01 node connection and pairing failures for 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

  • Diagnostics across local Wi‑Fi, Tailnet, and public URL scenarios to identify the correct route.
  • Guidance on restoring correct gateway bindings and approving pending device pairings.
  • Troubleshooting steps aligned with rx01 config states and QR results to minimize guesswork.

Quick Start

Diagnose the RX01 node connection and fix the active pairing route for the current setup.

Frequently Asked Questions about node-connect

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

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

Pairing fails when gateway.bind and gateway.remote.url configurations do not match the advertised public URL. Diagnose the active route to verify Tailscale status and ensure a deterministic path is correctly advertised to the client.

How do I fix an unauthorized or bootstrap token invalid error during RX01 device pairing?

Fix unauthorized or bootstrap token errors by diagnosing the device-pair flow and restoring correct gateway bindings. The process identifies misconfigured publicUrl settings and guides you through approving pending device pairings.

Does this diagnostic process support Android, iOS, and macOS companion apps for RX01?

Yes, the diagnostic process supports RX01 node connection and pairing failures across Android, iOS, and macOS companion apps. It handles QR setup code failures and manual host or port connections for supported platforms.

What is the best way to troubleshoot QR setup code failures for RX01 nodes?

Troubleshoot QR setup code failures by verifying gateway configurations and Tailscale status to identify the correct route. The process aligns troubleshooting steps with rx01 config states and QR results to minimize guesswork.

When should I manually check gateway configurations instead of using automated diagnostics for RX01?

Manually check gateway configurations when diagnostics cannot establish a deterministic route or when local Wi-Fi works but Tailnet does not. Verify gateway.bind, gateway.remote.url, and plugins.entries.device-pair.config.publicUrl settings directly.