node-connect

Diagnose OpenClaw node-to-gateway connectivity and pairing failures across network topologies.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill node-connect-tedtv1007-ctrl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/tedtv1007-ctrl/milk-skills-library/tree/main/node-connect
Command: npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill node-connect-tedtv1007-ctrl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves connectivity and pairing failures between OpenClaw nodes and gateways, eliminating ambiguity in network topology and authentication configurations.

Core Features & Use Cases

  • Topology Validation: Automatically identifies whether the connection issue stems from local LAN, Tailscale, or public URL configurations.
  • Diagnostic Automation: Executes a suite of OpenClaw CLI commands to verify gateway bindings, auth modes, and device pairing status.
  • Use Case: When a user reports that their mobile app cannot connect to their home gateway, this skill guides the AI to check the specific gateway bind mode and verify if a pending pairing request is blocking the connection.

Quick Start

Ask the AI to diagnose the connection failure by providing the specific error message from the app and the intended network route.

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 issues when my mobile app cannot reach the gateway?

To fix OpenClaw node connection issues, validate your network topology to determine if the failure is on the local LAN, Tailscale, or a public reverse-proxy. Provide the app error message to diagnose gateway bindings and pending pairing requests.

Why does my OpenClaw device pairing fail across Tailscale tailnets?

OpenClaw device pairing fails across Tailscale tailnets due to incorrect authentication states or gateway bind modes. Diagnostic automation checks device pairing status and verifies configuration parameters to ensure secure node registration and data transmission.

How to diagnose OpenClaw gateway configuration and authentication states?

Diagnose OpenClaw gateway configuration by running specific OpenClaw CLI commands that verify gateway bindings, auth modes, and device pairing status. This validates configuration parameters across local LAN, Tailscale, and public reverse-proxy setups.

Does node-connect troubleshooting work for public reverse-proxy network setups?

Yes, node-connect troubleshooting works for public reverse-proxy setups. It operates across diverse network topologies including local LAN, Tailscale tailnets, and public reverse-proxy configurations to resolve node-to-gateway communication failures.

What should I check when OpenClaw node-to-gateway communication is not working?

When OpenClaw node-to-gateway communication is not working, check the network route, gateway bind mode, and whether a pending pairing request is blocking the connection. Topology validation identifies if the connection issue stems from local LAN, Tailscale, or public URL configurations.