Use this page as an error index: match the symptom, then open the deep article. Don’t change subscription, reinstall, and Tun in the same minute—one layer at a time.
In five minutes: classify subscription vs proxy-fail vs Tun/ports vs AV. Logs beat rage clicks (logs).
Start here: classify in five minutes
| If this is true | The fault is probably | Go to |
|---|---|---|
| Import fails, or zero nodes after update | Subscription | Setup / no-nodes articles |
| Proxy “on” but some sites fail | Routing / DNS / Tun | Sites-not-opening, routing, DNS |
| Port already in use at launch | Ports / core comms | Ports, core communication |
| Fine until an upgrade | Config / leftover | Config location, backup, release notes |
| AV flagged the binary | False positive | Safety article |
Subscriptions and nodes
- Import spins/fails: setup, update failed.
- Update OK, zero nodes: no nodes.
- All timeouts / -1: latency, slow speed.
Tun, ports, proxy on but sites fail
- Tun/service install fails: Tun start failed, Tun.
- Port in use: ports; sometimes core communication.
- Proxy on, some sites fail: sites not opening, routing, DNS.
- Games/CLI/AI bypass proxy: Tun & AI, CLI proxy.
Resources, upgrades, AV
- RAM/CPU: CPU/RAM.
- Weird after upgrade: config location, backup, v2.5.6.
- AV quarantine: safety.
Don’t reinstall yet
No logs, one failed refresh, AV quarantine unchecked—wait. Reinstall when binaries are corrupt or the core still won’t start after cleanup. Recurring next day: autostart+update stacks, corp network, leftover processes.
Same-day rhythm
Classify → change one variable per deep article → write version + exact error text + tried steps. Paste raw messages when codes aren’t searchable. Reinstall hub: download center.