diagnose-connectivity

Diagnose 3x-ui client connection failures through ordered read-only panel checks.

5|3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/pyworkload/3x-ui-mcp --skill diagnose-connectivity-pyworkload
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose-connectivity
Source: https://github.com/pyworkload/3x-ui-mcp/tree/main/skills/diagnose-connectivity
Command: npx skills add https://github.com/pyworkload/3x-ui-mcp --skill diagnose-connectivity-pyworkload

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a 3x-ui proxy client reports "it stopped working", this Skill provides a systematic, fastest-first diagnostic sequence that isolates whether the cause is the Xray core, the inbound, the client's own limits, routing and outbounds, or the node — using only read-only MCP tool calls. ## Core Features & Use Cases - Scoped triage: Classifies the outage as panel-wide, per-inbound, per-client, or per-destination before running any checks, so diagnosis starts at the right layer. - Client limit inspection: Checks enable flags, expiryTime, totalGB quotas, limitIp, and HWID device slots, and decodes common Xray log lines such as flow mismatches for VLESS Vision. - Routing and outbound verification: Uses test_route, test_outbound, balancer and geodata checks to find why a destination fails while the connection itself works. - Use Case: A user reports one client cannot connect while others work fine. The Skill walks through get_client, get_client_traffic, and get_last_online to discover the client's expiryTime passed, distinguishing it from a network failure. ## Quick Start Ask the assistant to diagnose why a 3x-ui client cannot connect, providing the client's email or a description of who is affected.

Frequently Asked Questions about diagnose-connectivity

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

FAQPage Schema
How do I troubleshoot a 3x-ui client that cannot connect?▼

Start by scoping the outage with get_online_clients, then check the Xray core logs, the inbound's enable/port/expiry settings, and the client's own limits such as expiryTime, totalGB, and limitIp. The Skill orders these checks so the most common causes are found first.

Why did all my 3x-ui clients drop at the same time?▼

A panel-wide outage is usually a saved Xray template the core refuses to load. Compare get_xray_config with get_xray_template and read get_xray_logs to find the offending field, then fix the template and restart Xray.

What do Xray flow mismatch errors like xtls-rprx-vision mean?▼

The xtls-rprx-vision flow only works on TCP with TLS or REALITY. Errors mean either the flow is set on a ws/grpc/xhttp inbound, or the client link lacks the flow parameter the server expects; clear or reissue the flow accordingly.

Why does a domain rule in 3x-ui routing not match traffic?▼

Domain rules require sniffing enabled on the inbound, otherwise the router only sees IP addresses. Also check rule order with get_routing_rules, since a broad rule above a narrow one swallows it, and validate geosite/geoip tokens with validate_geodata_tokens.

Can diagnosing connectivity reset traffic counters or delete clients?▼

No. Every diagnostic step is read-only. The Skill explicitly warns against running destructive panel-wide tools like reset_all_traffics or delete_depleted_clients during diagnosis, since they destroy evidence and accounting data.