Network checks and connections
Windows / macOS network check
- Keep the failing profile and network environment.
- Open Tools → Network Check and run it.
- Review failures and attention items before taking their suggested actions.
- Rerun after each fix and retest the original application.
Checks cover the active profile, core, listeners, system proxy, TUN, DNS and a few HTTPS probes. Passing does not prove that every node, app, UDP or IPv6 path works.
| Result | Next check |
|---|---|
| No traffic capture | Enable System Proxy/TUN or configure the app |
| Local port failure | Running core and port conflicts |
| System proxy mismatch | Competing software or organization policy |
| TUN route mismatch | Authorization, other VPNs and routes |
| System path works, proxy fails | Node, rules and core DNS |
The system network path may still use TUN; it is not necessarily a physical direct connection. Cancelled checks or profile changes can leave incomplete results.
Other platforms and routing
On Android/Linux, use connections and logs. Filter by the target domain, inspect the rule/group/outbound, then create a fresh connection after changing settings.
Review personal data before copying reports. Include version, time, network type and reproduction steps in a support ticket, never full tokens or subscriptions in public issues.