Error cheat sheets miss long-tail failures. Clash Verge Rev’s Connections and Logs pages answer whether traffic entered the client, whether it was PROXY or DIRECT, and whether failures look like DNS, auth, or timeouts—including Cursor/Claude cases.
Order: Connections classify → Logs name the error → then change node, rules, or toggles. Index: common errors.
Connections: three questions
- Any new hits? No → system proxy / Tun.
- PROXY or DIRECT? Unexpected DIRECT → routing.
- PROXY but still failing → nodes/DNS/site (latency, DNS, sites blocked).
Logs: raise level, reproduce once
Temporarily raise log level, reproduce one action, then search timeout, dns, auth, reject, yaml, parse. Updates: update failed. Change one variable at a time.
# keywords worth grepping in the Logs page
timeout dns auth
reject yaml parse
AI and CLI
Trigger one minimal request and watch Connections (Tun & AI, CLI proxy). No hits → path broken. Hits but errors → region/node or credentials.
Mini example
"Proxy on, Google spins": no hits → fix system proxy; DIRECT → rules/mode; PROXY → swap node and read dns vs timeout in logs. Speed: slow speed.
Stop
Bring one log line + a Connections screenshot when asking for help. Builds: download center.
Where each symptom shows up
| You see | Read this first |
|---|---|
| No connection rows at all | Connections page → path not entering Clash |
| Rows marked DIRECT unexpectedly | Connections + routing rules |
| Rows show 403 / timeout | Logs page → node or region |
| Core banner / won’t start | Logs page → panic / bind error |