How To Set Up System Proxy in Clash Verge Rev on Windows
Understand what the Windows system proxy switch does
Clash Verge Rev can route Windows applications through a local proxy service provided by its active Clash or Mihomo core. The System Proxy switch does not send traffic directly to a remote node by itself. Instead, it changes the Windows proxy settings so applications that respect the operating system proxy configuration connect to Clash Verge Rev’s local HTTP or mixed port. The core then evaluates the request against the active mode, proxy groups, DNS settings, and rules.
This distinction explains why enabling the switch may work immediately in one application but appear to have no effect in another. Browsers, office applications, download tools, terminals, games, and background services do not all use the Windows proxy API in the same way. Some read the system proxy automatically, some have their own proxy page, and some connect directly unless they are configured separately. System Proxy is therefore a convenient application-level integration method, not a guarantee that every packet on Windows will pass through Clash.
Before changing anything, make sure Clash Verge Rev is running, a configuration has been selected, and the core is active. The client may display the interface even when the core failed to start, when the imported profile contains an invalid field, or when the local listening port is occupied by another program. The system proxy switch can be turned on in these situations, but applications will receive connection errors because there is no usable local service behind the Windows proxy address.
There are three separate questions to verify:
- Is the Clash Verge Rev core running and listening on the expected local port?
- Is Windows configured to use that local address and port?
- Does the application being tested actually read the Windows proxy configuration?
Keeping these questions separate makes troubleshooting much faster. If the core is stopped, changing Windows settings will not help. If Windows points to the wrong port, a healthy core will still appear unreachable. If the application ignores Windows proxy settings, the system switch may be working correctly even though that application continues to connect directly.
Check the active core, profile, and listening port
Open Clash Verge Rev and select the profile you intend to use. A profile may come from a subscription, a local YAML file, or a generated configuration. Confirm that it has loaded successfully and that proxy groups contain usable entries. If the profile is empty, expired, or still being updated, the client may not be able to establish a useful connection even though its window opens normally.
Next, check the client’s settings for the local HTTP, SOCKS, or mixed port. The exact menu names can differ between Clash Verge Rev releases, and an imported configuration may override the familiar default. Do not assume that the port is always 7890. A typical configuration may look like this:
mixed-port: 7890
allow-lan: false
mode: rule
log-level: info
In this example, mixed-port accepts both HTTP proxy requests and SOCKS5 requests on port 7890. A configuration using separate ports might instead contain port for HTTP and socks-port for SOCKS5. Windows system proxy settings generally need an HTTP-compatible endpoint. A SOCKS-only port should not be entered as though it were an HTTP proxy unless the application explicitly supports that protocol.
| Setting | Typical purpose | What to verify |
|---|---|---|
port |
HTTP proxy listener | Use this when the client exposes a separate HTTP port. |
socks-port |
SOCKS5 proxy listener | Use it only in applications that support SOCKS5. |
mixed-port |
Combined HTTP and SOCKS5 listener | Often the simplest local endpoint for desktop testing. |
allow-lan |
Controls access from other devices | It does not need to be enabled for local Windows applications. |
For a local Windows setup, the proxy address is normally 127.0.0.1 or localhost. If the client is configured to bind only to the loopback interface, other devices on your network cannot use that port, but applications on the same computer can. Enabling LAN access unnecessarily increases the number of devices that can reach the proxy, so leave it disabled unless you have a specific reason to share the service.
You can verify whether the selected port is listening with PowerShell. Replace 7890 with the actual port shown by Clash Verge Rev:
Test-NetConnection 127.0.0.1 -Port 7890
A successful result usually shows TcpTestSucceeded : True. This only confirms that a process accepts a TCP connection on the port; it does not prove that the active node, routing rules, or remote connection work correctly. If the test fails, inspect the Clash Verge Rev log, change to an unused port, reload the profile, and check whether another proxy client is already running.
Enable System Proxy in Clash Verge Rev
Once the core and local port are ready, use the main Clash Verge Rev window to locate the System Proxy toggle. In many builds it appears on the dashboard or in a general settings area. Turn it on and wait a few seconds for Windows to apply the change. Avoid enabling several proxy applications at the same time; two clients can repeatedly overwrite the same Windows proxy fields and create the impression that the switch does not stay enabled.
The Windows setting can be checked independently from the client. Open Settings, choose Network & internet, and open Proxy. Under the manual proxy area, Windows should show a local server address and the port configured by Clash Verge Rev. The exact wording and layout can vary between Windows 10 and Windows 11, but the important values are the same: a loopback address such as 127.0.0.1 and the active Clash listener port.
- Start Clash Verge Rev and load a valid profile.
- Confirm that the core is running and that the local HTTP or mixed port is known.
- Turn on the client’s System Proxy switch.
- Open Windows proxy settings and confirm the local address and port.
- Open a new browser window and test a website that was not already cached.
- Return to the Clash Verge Rev connection view and look for the new request.
The connection view is more useful than a successful page alone. A page can load from the browser cache, through a browser extension, or through an existing connection that was established before the setting changed. Open a new domain, refresh it, and check whether Clash Verge Rev records the destination, matched rule, selected proxy group, and connection status. If a new request appears there, the browser is reaching the running core through the expected path.
If Windows shows a manually configured proxy but the values do not match Clash Verge Rev, disable the system proxy from the client, correct the conflicting setting, and enable it again. Some VPNs, privacy tools, corporate management policies, and older proxy utilities can change Windows proxy settings without displaying a warning in Clash Verge Rev.
Configure automatic startup and reliable proxy behavior
Many users expect the system proxy to remain usable after restarting Windows. That requires more than turning on the switch once. The client must start, the core must load a profile, the local listener must become available, and the Windows proxy setting must point to that listener. If any step happens in the wrong order, Windows applications may start before Clash Verge Rev is ready and report temporary connection failures.
Enable client startup carefully
Look for a setting such as Launch at startup, Start with Windows, or a similar option in Clash Verge Rev. Enable it only after confirming that the current profile can load without manual intervention. If the client asks whether it should start minimized or run in the background, choose the behavior that matches your workflow. A minimized client can still provide the proxy, but it may be harder to notice when the core has stopped or a profile update failed.
Startup and System Proxy are related but separate options. A client may start with Windows while leaving System Proxy disabled, or it may restore the proxy switch before the core is ready. After enabling startup, restart Windows and check the sequence: Clash Verge Rev should appear or run in the tray, the profile should be active, the listener should accept connections, and Windows should still contain the expected local proxy values.
Avoid competing clients and stale settings
Do not run Clash Verge Rev together with another Clash client, a legacy proxy manager, or a VPN application that manages the Windows proxy automatically unless you understand which program has priority. A common symptom of this conflict is that the toggle turns on and then turns off, or that Windows displays a port different from the one shown in Clash Verge Rev.
Some workplace or school computers also apply proxy settings through policy. If the manual proxy fields are locked, revert after a short delay, or cannot be edited, the change may be controlled by Windows management rather than the Clash client. In that case, check the device policy or contact the administrator instead of repeatedly toggling the client.
Use the following startup checklist after a reboot:
- Confirm that the expected Clash Verge Rev process is running.
- Confirm that the selected profile is still active and not awaiting an update.
- Check the local port with PowerShell if applications cannot connect.
- Verify that Windows still shows the loopback address and correct port.
- Test a fresh browser request and inspect the Clash connection log.
Test browsers and applications with the right method
A browser is a practical first test because most Windows browsers can use the operating system proxy. Close existing tabs or open a private window, then visit a domain that has not been opened recently. Disable browser proxy extensions during this test. If an extension remains active, the request may use the extension’s own proxy and give a misleading result.
Testing should include both a page load and the Clash connection log. A page that loads does not identify which route was used. A matching entry in the log shows that the request reached the running core, although the final route still depends on the selected rule and proxy group. If the browser works but no request appears in Clash Verge Rev, review browser-specific proxy settings, extensions, secure connection tools, and other network software.
Command-line programs need separate attention. Some tools honor Windows proxy variables, some read WinHTTP settings, and others require explicit options. For example, a terminal session may not automatically use the same proxy path as a browser. You can test an HTTP-compatible local listener with a command such as:
curl.exe -x http://127.0.0.1:7890 https://example.com
Replace the address and port with the values shown in Clash Verge Rev. This command explicitly tells curl which local proxy to use, so it is useful for separating a broken core from a terminal that simply ignores Windows proxy settings. If the explicit request works but a normal command does not, configure that tool’s proxy option or environment variables according to its own documentation.
| Application type | Likely behavior | Recommended test |
|---|---|---|
| Most desktop browsers | Often follows Windows proxy settings | Disable extensions and inspect the Clash connection log. |
| Terminal utilities | May ignore Windows system proxy | Use an explicit proxy option or tool-specific environment variables. |
| Games and launchers | Frequently uses direct sockets | Check whether the application supports a proxy or use TUN when appropriate. |
| Background services | May run under another account or service context | Review the service’s own network configuration and permissions. |
Fix settings that revert or fail to connect
If the System Proxy switch immediately turns off, first check whether the Clash core is still running. A failed configuration load, unavailable port, permission issue, or unexpected application exit can cause the client to remove the Windows proxy setting to avoid leaving a broken endpoint behind. Read the runtime log instead of assuming that the switch itself is defective.
If the switch remains on but browsers cannot connect, compare the Windows proxy port with the active Clash port. Profiles can change ports after an update, and another client may have changed the Windows value. Also check whether the address uses 127.0.0.1 rather than an unreachable LAN address. If the port is correct, test it with PowerShell and then examine the Clash connection log for rejected or failed requests.
If only HTTPS sites fail, do not immediately add random TLS options to the profile. First determine whether the browser reaches the local proxy at all. A local proxy normally receives the browser’s CONNECT request for an HTTPS destination and then applies the configured routing. A failure can result from a stopped core, an incorrect proxy protocol, DNS problems, a rejected rule, or a remote node that cannot establish the destination connection.
If traffic uses the wrong node, inspect rule mode and proxy-group selection. System Proxy only delivers traffic to the core; it does not choose the final exit. In rule mode, the domain or IP is matched from top to bottom. A broad rule placed above a more specific rule can send traffic to an unexpected group. Check the matched rule and selected group in the connection details before editing the configuration.
Finally, reset the setup in a controlled order if the values remain inconsistent. Turn off System Proxy, close other proxy and VPN tools, confirm that Clash Verge Rev can start its core and listen on a free port, then enable the system proxy again. This is safer than editing several Windows fields and profile options at the same time because each change can be tested independently.
Frequently asked questions
Does System Proxy route all Windows traffic?
No. It normally affects applications that read the Windows proxy configuration. Programs using direct sockets, their own proxy settings, a separate VPN tunnel, or a service account may bypass it. TUN mode is designed for broader interception, but it has different permissions and compatibility requirements.
Which port should I enter in Windows?
Enter the HTTP or mixed port exposed by the running Clash Verge Rev core, not a port chosen from memory. A mixed port is often convenient because it accepts HTTP and SOCKS5 requests, while a SOCKS-only port should be used only by applications that explicitly support SOCKS5. Confirm the current value in the client and test it locally.
Why does the proxy toggle keep reverting?
The core may have stopped, the profile may have failed to load, the port may be occupied, or another proxy application may be rewriting Windows settings. Check the Clash Verge Rev log, compare the Windows address and port with the client, and temporarily close competing network tools.
Should I enable startup together with System Proxy?
Enable startup if you want the client available after Windows launches, but test the complete sequence after a reboot. The client must load a valid profile and start the core before applications use the local proxy. If startup restores a broken proxy setting, disable automatic proxy restoration until the profile and port are reliable.