Client runs but the system proxy is inactive
Not every client takes over all apps automatically. Turn the system proxy on manually, or confirm you are in TUN mode.
Connectivity troubleshooting
Client runs but there is no internet
A running client does not mean traffic is routed. Work down through system proxy, port, DNS, and rules.
Content reviewed · Nov 3, 2026
Who it is for
People whose client says it is running, but the browser, terminal, or a specific app cannot connect.
Before troubleshooting
- The profile loaded and shows nodes
- You know the client’s listening port
- A plain web page to test against
Troubleshooting steps
- 1
Establish the scope first: everything broken, or one app? Everything points at the system proxy; one app points at that app’s settings.
- 2
Check that the system proxy switch is actually on, and that the address and port point at the client.
- 3
Check whether another process took the port; clients sometimes fall back to a different one.
- 4
Check DNS: if raw IPs connect but names do not resolve, it is a DNS problem.
- 5
Touch rules and TUN last, and build up from a minimal profile.
Common issues
Only some apps fail
Those apps may bypass the system proxy: some games, terminal tools, containers. Configure them individually or use TUN.
Next step
If the problem started after enabling TUN, read the TUN troubleshooting guide.
Read next：How to verify a download is official