Setting up Clash Verge on Windows 11 involves more than pasting a link and pressing Connect. You need a compatible client, a current subscription URL, an imported profile, a selected route, and a connection mode that matches what you want to do. This guide walks through those steps in order, then shows how to check the public IP address and isolate common update or connection problems.
Clash Verge is a desktop client for managing proxy configurations; it is not itself a subscription or a single VPN protocol. A subscription supplies configuration data, while the client uses that data to create profiles and route traffic. Menu labels can differ slightly between versions, so look for equivalent terms such as “Profiles,” “Subscriptions,” “Update,” or “System Proxy” if your interface is not an exact match.
Prepare Windows 11 and Clash Verge
Start by confirming that you have access to a current subscription URL and that the Windows account can install desktop software. Get the client from a source you trust, such as the service’s download page or the project’s official distribution channel. Avoid repackaged installers and download links sent by unknown accounts. If you are unsure which Windows build to choose, check the instructions shown by the source rather than guessing from the computer’s processor name.
Install the application using the downloaded installer, then open Clash Verge. Windows may show a security prompt when the client needs permission to install or operate a network component. Read the prompt and confirm that the publisher and application match the software you intended to install. Do not approve an unexpected prompt just to make the setup proceed.
On first launch, Windows Defender Firewall may ask whether the application can communicate on private or public networks. Choose settings appropriate to the network you are using and the permissions requested. Network permissions and administrator approval are separate from the subscription itself: granting one does not add a profile or make an unavailable route work.
Before importing anything, check the client’s status area for an error or a request to install a service. Some features, particularly TUN mode, may require elevated permission or a supporting system service. You do not need to enable every advanced feature just to test a basic connection. Begin with the least complicated mode available in your version, then add system-level options only if your use case requires them.
Get and protect the subscription URL
Sign in to your service account and locate the subscription or client-configuration area. Copy the URL intended for a Clash-compatible client. If the service provides platform-specific links, choose the one marked for Clash, Clash Verge, or a compatible configuration format. Do not copy a normal website address, a single server address, or a login-page link in its place.
A subscription URL often contains a long token that grants access to configuration data. Treat it like a password: do not post it in a public forum, send it in an untrusted screenshot, or paste it into an online URL checker. If you think it has been exposed, use the service panel’s available controls or contact support to learn whether it can be refreshed. Removing a link from a chat does not necessarily invalidate it.
If the account page offers a copy button, use it and check that the complete address has been copied. When copying manually, make sure there are no leading or trailing spaces, line breaks, or quotation marks. A truncated URL can look plausible but fail when the client tries to download its profile.
- Open the account panel and locate the subscription address for a compatible client.
- Copy the complete URL without adding spaces or punctuation.
- Keep it private and avoid saving it in a shared document or public message.
- Return to Clash Verge and use its subscription or profile import function.
If you need help finding the right client workflow, see the setup guide. The exact account-panel labels may vary, but the important point is to retrieve the subscription URL rather than trying to import an individual route as though it were a full profile.
Import and update the profile
In Clash Verge, open the page or panel used to manage profiles. Choose the option to add a profile from a URL, add a subscription, or import a remote configuration. Paste the address you copied, give the profile a recognizable name if the client asks for one, and save it. If the client offers a profile type, select the subscription or remote-profile option rather than a local file unless you were specifically given a configuration file.
After saving, use the profile’s update control. A successful update should leave the profile visible and make its proxy groups or routes available in the client. If an error appears, note its wording before changing settings. A timeout, an invalid response, and a parsing error point to different causes: connectivity, a wrong or expired URL, and an incompatible or malformed configuration are not the same problem.
Some profiles can refresh automatically, while others require a manual update. Automatic refresh is useful for keeping configuration current, but it does not mean that every connection problem will be fixed by repeatedly refreshing. Update once after importing or when you have a clear reason to suspect the profile is outdated. If the service says the URL has changed, replace the saved address with the current one rather than continuing to retry an old link.
Once the profile is present, open its details and confirm that the client has loaded usable proxy groups or routes. A profile name by itself is not proof that the configuration was retrieved successfully. If the list is empty, the import may not have completed, the URL may be intended for another client format, or the response may not contain a configuration Clash Verge can parse.
Choose a route and connect
Open the proxies or groups view and inspect the available choices. A profile may contain named regions, manual-selection groups, or automatic groups. The exact labels depend on the configuration supplied by the service. If a group offers a manual choice, select a route that matches your intended destination and access needs. If it is an automatic group, allow it to select according to its configured rules rather than expecting every group to behave like a list of independent servers.
Next, decide how traffic should be handled. Rule mode generally applies the profile’s rules to determine which requests use a proxy and which go directly to the local network. Global mode generally routes more traffic through the selected proxy group. Direct mode bypasses proxy routing. For a first connection check, use a mode whose behavior you understand and remember to distinguish “the client is connected” from “this particular application uses the proxy.”
System Proxy and TUN are different ways of applying routing on Windows. System Proxy changes the operating system’s proxy settings for applications that respect them; some software may ignore those settings. TUN mode uses a virtual network interface to capture a broader range of traffic, but it may need additional permissions and can affect routing more extensively. You do not have to enable both. Start with the simpler option, and change one setting at a time if an application is not following the expected route.
Connect from the client’s main control. Wait for its status to settle, then try a simple network request in a browser. If the interface shows a successful connection but no pages load, do not immediately switch through every route. Check whether the selected group has an active choice, whether the current mode should route the browser, and whether the Windows network itself can reach the internet with the client disconnected.
- ✅ Confirm that the profile updated and that proxy groups or routes are visible.
- ✅ Select a route or group that is available in the imported configuration.
- ✅ Start with a connection mode whose traffic behavior you understand.
- ❌ Do not run multiple proxy clients at the same time; their system settings or routes may conflict.
- ❌ Do not assume that every Windows application follows the system proxy.
Check the public IP and traffic
After connecting, verify the result rather than relying only on the client’s “Connected” label. Open a public IP lookup page and compare the displayed address and approximate location with what you see when the client is disconnected. If the result does not change, first consider whether the browser is using a direct rule, whether System Proxy is enabled, and whether the selected group actually has a route selected.
You can use the site’s IP lookup page for this check. The displayed location is an estimate based on IP-address information and may not precisely match a city or physical server location. The useful comparison is whether the browser request appears to leave through the expected network path, not whether a location database names the exact building or city.
Test more than one type of request if your goal is to use applications beyond a browser. A browser can follow Windows system-proxy settings while another app uses its own network stack. If the browser changes to the expected exit address but a particular application does not, inspect that application’s proxy behavior and the client’s routing mode before treating the whole profile as broken.
When the IP lookup page cannot load, test an ordinary website and check the client’s connection log. If nothing can connect, the issue may be the route, local network, DNS, or a system-level routing conflict. If only some destinations fail, the profile’s rules or the destination’s own availability may be involved. Keep the checks specific: note which application fails, whether it fails only while connected, and whether the client reports a connection or DNS error.
Troubleshoot import and connection errors
The subscription will not update
Check the subscription URL first. Confirm that it is complete, current, and intended for a compatible client. Replace it if the service panel provides a newer address. Then verify that Windows has internet access independently of Clash Verge and that no local firewall or security product is blocking the client’s request. If the error mentions a timeout, retry after confirming the local connection; repeated attempts with an unchanged network condition are unlikely to reveal a different cause.
If the client reports a parsing or format error, copying the URL again may not solve the problem. Check that you chose the Clash-compatible subscription option and that the service’s configuration format is supported by the client version you installed. If the service has recently changed its subscription format, consult its current client instructions or support rather than editing configuration fields at random.
The profile loads, but no route works
Confirm that you have selected an actual route or a functioning proxy group. Some configurations display groups that require you to choose a member before traffic can flow. Check the client’s logs for failed connections, DNS errors, or a message that identifies a rejected handshake. If the same route repeatedly fails, test a different available route and keep the mode and application unchanged so you can tell whether the route was the difference.
Also check whether another VPN or proxy application is active. Two clients can compete to control Windows proxy settings, DNS, or routing. Disconnect the other client before testing Clash Verge, then reconnect and verify the result. If you changed between Wi-Fi and another network, disconnect and reconnect the client so it can establish a fresh session using the current network.
The client says connected, but pages do not open
Check the route selection, mode, DNS behavior, and Windows proxy status in that order. Try another browser request and compare with the client disconnected. If the connection works only when the client is off, inspect the profile rules and system routing rather than assuming the internet provider is down. If direct browsing also fails, restore the local network first; a proxy client cannot repair an underlying Wi-Fi or broadband outage.
Use TUN mode only when you need broader application coverage or when the simpler system-proxy method is insufficient. If you enable it, follow the client’s permission prompts and confirm that the required service is running. If turning it on causes new conflicts, turn it off and return to the previous known state before trying another change. Changing several advanced settings together makes it difficult to identify which one caused the problem.
Once the profile updates, a suitable route is selected, and the IP check behaves as expected, the basic setup is complete. Keep the subscription URL private, refresh the profile when the service instructs you to, and use the connection log when behavior changes. For additional client and network troubleshooting steps, see the troubleshooting manual.