Troubleshooting Guide¶

Common Issues¶

Proxies Showing alive=false¶

Symptoms: Router dashboard shows LA-VMess and LA-VLESS with alive=false status

Root Cause: Xray mux enabled with SOCKS5 backend causes TLS handshake failures

Solution: See complete fix in Mux Fix Guide

Quick fix:

# On VPS
ssh root@vmiss.ata.lol
cd /root/proxy-stack
# Edit xray/config.json, set mux.enabled = false
docker compose restart xray

Slow Domestic Website Access¶

Symptoms: Baidu, Taobao, JD.com slow or timing out

Root Cause: Incorrect routing rules or domestic sites being proxied

Solution:

# On router
curl http://127.0.0.1:9090/rules | grep -i baidu
# Should show: DIRECT, not PROXY

# If wrong, update Loyalsoldier rules
# OpenClash dashboard → Rule Sets → Update All

International Sites Not Accessible¶

Symptoms: Google, Facebook, TikTok.com unreachable

Root Cause: Proxy down, exit node issues, or rule misconfiguration

Troubleshooting Steps:

1. Check proxy health:

   curl -s http://127.0.0.1:9090/proxies/LA-VMess | jq '.alive'
   # Expected: true
   

2. Check exit node:

   ssh root@vmiss.ata.lol
   curl --socks5 proxy.starzone.io:51313 https://ipinfo.io/ip
   # Should return: 168.148.92.254
   

3. Check VPS logs:

   ssh root@vmiss.ata.lol
   cd /root/proxy-stack
   docker compose logs xray --tail 100
   

WiFi Not Broadcasting¶

Symptoms: WiFi SSID not visible after router configuration

Solution:

# Check WiFi enabled
uci show wireless | grep disabled
# Should show: disabled='0'

# If disabled='1', enable it:
uci set wireless.@wifi-iface[0].disabled='0'
uci commit wireless
wifi reload

High Latency / Slow Speed¶

Symptoms: All connections slow, high ping times

Troubleshooting:

1. Check ISP connection:

   ping -c 10 baidu.com
   # Should be <50ms
   

2. Check VPS latency:

   ping -c 10 vmiss.ata.lol
   # Should be <250ms
   

3. Check bandwidth usage:

   # OpenClash dashboard → Connections
   # Look for heavy traffic connections
   

Solutions: - If ISP slow: Contact ISP - If VPS slow: Check VPS CPU/bandwidth limits - If specific app slow: Add custom rule to bypass proxy

Emergency Procedures¶

Complete Service Outage¶

1. Verify router powered on and WAN connected

2. Restart OpenClash:

   ssh root@router-ip
   /etc/init.d/openclash restart
   

3. If still down, check VPS:

   ssh root@vmiss.ata.lol
   docker ps
   # If containers not running:
   cd /root/proxy-stack
   docker compose up -d
   

4. Last resort - disable proxy temporarily:

   # On router
   /etc/init.d/openclash stop
   # Clients will use direct connection
   

Customer Cannot Access Any International Sites¶

Quick Fix (Temporary):

# Switch to backup proxy
# OpenClash dashboard → Proxies → Select LA-VLESS

Permanent Fix: - Investigate LA-VMess issue - See Mux Fix Guide for common problems

Debugging Tools¶

Check Egress IP¶

curl https://ipinfo.io/ip
# Expected: 168.148.92.254 (or customer-specific IP)

Test Proxy Manually¶

curl --proxy http://127.0.0.1:7890 https://www.google.com
# Should return Google homepage HTML

View OpenClash Logs¶

tail -f /tmp/openclash.log

View Clash Core Logs¶

logread | grep clash

Getting Help¶

For issues not covered here:

1. Check System Reference for operational procedures
2. Check Mux Fix Guide for proxy issues
3. Review VPS logs: docker compose logs xray caddy
4. Contact technical support (Enterprise customers: 2-hour response time)

Related Documentation: - System Reference - Mux Fix Guide - Configuration Guide