node-connect

Diagnose node-to-gateway connection and pairing issues across Android, iOS, and macOS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps administrators diagnose and fix node-to-gateway connection and pairing failures across devices and platforms for OpenClaw, ensuring reliable remote access and device pairing.

Core Features & Use Cases

  • Guided troubleshooting: Step-by-step checks to identify whether the problem is local, LAN, Tailnet, or public URL routing.
  • Cross-platform compatibility: Applies to Android, iOS, and macOS companion apps, including QR/manual pairing scenarios.
  • Use Case: When setup reports "pairing required" or "unauthorized," use this skill to verify gateway URL, authentication, and routing, and apply a safe corrective path.

Quick Start

Follow the guided prompts to run the diagnostic and initiate a fix sequence for the detected route.

Frequently Asked Questions about node-connect

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

FAQPage Schema
How do I troubleshoot node-to-gateway connection issues across local and Tailnet routes?

To troubleshoot node-to-gateway connection issues, use guided diagnostic checks to identify whether the failure originates from local, LAN, Tailnet, or public URL routing, then apply a safe corrective sequence for the detected path.

Why does my device pairing report unauthorized or pairing required errors?

Pairing reports unauthorized or pairing required errors when gateway URL configuration, authentication tokens, or routing statuses are invalid, requiring canonical verification checks before applying fixes to restore access.

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

Yes, this diagnostic process supports Android, iOS, and macOS companion apps, applying canonical checks and fixes to validate gateway URLs, authentication, and connection status for both QR and manual pairing scenarios.

What is the best way to diagnose Tailnet routing failures for remote device access?

The best way to diagnose Tailnet routing failures is running step-by-step checks that validate gateway URLs and authentication status, ensuring reliable remote access before applying any configuration changes.

How to validate gateway URLs and authentication before applying configuration fixes?

Validate gateway URLs and authentication by following guided prompts that specify concrete config checks and guardrails, verifying connection status across local, LAN, Tailnet, and public URL routing scenarios.

When should I not use manual configuration changes for node connection troubleshooting?

You should avoid manual configuration changes during node connection troubleshooting until guided diagnostic checks validate the gateway URL, authentication status, and routing path, ensuring safe corrective actions are applied.