01

It is a notice, not an enforcement

Switching on the system proxy does one thing: it points the proxy settings of your operating system at the local mixed port. Recent installs default to 7897; an older profile may still be on 7890.

After that it is up to each program. Ones that read the setting go through Clash Verge. Ones that do not keep connecting directly, and nothing in the app can force them.

So a whole category of reports are not bugs. The browser works but a game still connects directly, or a command line tool still times out fetching packages. Those programs never looked at the setting.

Check the port before you blame the app
On Windows, Settings then Network and Internet then Proxy shows the live value: 127.0.0.1 with your mixed port.

SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes
02

Three things decide who obeys it

  1. 1

    Sort your programs into two piles

    Mainstream browsers and most desktop applications read the system proxy. Games, download tools and command line utilities often do not, and some keep their own proxy configuration. For those, enter 127.0.0.1 and your mixed port in the program itself, or move to TUN.

  2. 2

    The bypass list decides what stays direct

    Loopback addresses and common private ranges are there by default, plus a <local> entry on Windows. Add your intranet domains, the NAS and the router address yourself, or internal services take a long detour to a remote node and often do not open at all.

  3. 3

    Keep one path open

    Running the system proxy and TUN together is rarely worth it. Their coverage overlaps heavily, so nothing gets faster, and working out which path a broken request took becomes much harder.

03

How you quit decides your next boot

This is where people get caught. End the process from Task Manager while the system proxy is on, or force a shutdown with the power button, and the operating system keeps pointing at 127.0.0.1 with nothing listening there. At next boot nothing reaches the internet. Quitting from the tray lets the app clear the setting on the way out.

  • Quit from the tray menu instead of ending the process
  • Run either the system proxy or TUN, never both
  • Keep intranet domains and the NAS address in the bypass list
04

Common questions

Clash Verge is closed but the browser still says a proxy server is in use.

The last session did not exit cleanly, so the setting stayed enabled while nothing listens on 127.0.0.1. Start Clash Verge, toggle the system proxy off, then quit from the tray. Or turn manual proxy setup off under Settings, Network and Internet, Proxy.

The browser goes through the proxy but one program refuses to. Can it be fixed?

That program does not read the system proxy. Look through its own settings: if it has a proxy or network section, enter 127.0.0.1 and your mixed port. If not, TUN is the only option, because it works at the adapter level and needs no cooperation.