Starting with a blank Clash Verge Rev installation, the quickest route to a working connection is to add a subscription URL, download its profile, choose a proxy node, and verify that traffic is actually using the proxy. A subscription is a provider-managed link that lets the client retrieve a configuration and refresh it later; it is not the same thing as a single proxy address. This guide walks through the complete setup, explains the choices you will see in the interface, and shows how to diagnose the most common problems without exposing your subscription credentials.
Before You Add a Subscription
First, obtain a subscription URL from a provider you trust. It is usually an HTTPS link containing a long, unique token. Treat that URL like a password: anyone who gets it may be able to download your configuration or use the service, depending on the provider’s controls. Do not post it in screenshots, public support forums, shared documents, or untrusted online “subscription converters.” If you need help, redact the token and any account identifiers before sharing diagnostic information.
Confirm that the service supports Clash or Mihomo-compatible subscriptions. Clash Verge Rev uses the Mihomo core, but a provider may offer several link formats, such as links for another client, a plain configuration file, or a general-purpose subscription converter. Choose the Clash/Mihomo option when the provider offers one. A link intended for a different client might return an incompatible format, even if it opens successfully in a browser.
It also helps to know the difference between a profile and a node. The profile is the configuration downloaded from your subscription. It can contain proxy nodes, proxy groups, routing rules, DNS settings, and other options. A node is one individual proxy endpoint listed within that configuration. You normally add and update the profile first, then choose a node or a proxy group from the client’s main controls.
- Install or open a current Clash Verge Rev release and allow it to use the Mihomo core.
- Make sure the computer has an internet connection that can reach the provider’s subscription server.
- Copy the complete subscription URL from the provider’s account page, including its scheme, such as
https://. - Check whether the provider requires a separate authorization step, account activation, or a specific Clash-compatible link.
Add the Profile URL
Open Clash Verge Rev and go to its profile management area. Depending on the release and language settings, the page may be called Profiles, Subscriptions, or something similar. Look for an action to add a remote profile, import a URL, or create a subscription. Paste the complete URL into the address field. If the interface offers a name field, choose a label that helps you recognize the provider, such as “Personal subscription” or “Travel profile.” Avoid placing the URL token itself in the label.
When you confirm the addition, the application contacts the subscription server and downloads the configuration. A successful import typically creates a profile entry and displays its name, update time, or status. Select that profile if it is not already active. In some versions, importing a profile does not automatically make it the current configuration, so check for an explicit option such as Use, Activate, or a selection control.
The first download can fail for reasons that are unrelated to the proxy nodes. The subscription URL may have been copied with an extra space or missing character, the provider may be temporarily unavailable, or the computer’s current network may block access to the subscription host. A browser test can sometimes help determine whether the address is reachable, but do not leave the full URL in browser history on a shared device. A successful browser response also does not guarantee that the returned content is a valid Clash profile.
If the client reports an unsupported format or a parsing error, check that you selected the correct subscription type at the provider. Do not immediately edit the downloaded configuration by hand: subscription profiles are often refreshed from the provider, and local edits may be overwritten. If the provider’s link is intended for Mihomo but still fails, check for a newer application release and ask the provider whether its output includes Mihomo-specific fields that require a compatible core.
Refresh and Activate the Profile
A subscription profile is a snapshot of the configuration available when it was last downloaded. Providers may add or remove nodes, change server details, or adjust proxy groups. After the initial import, refresh the profile so that Clash Verge Rev retrieves the provider’s latest version. Use the refresh or update action beside the profile, then wait for the operation to finish before testing a node. Avoid repeatedly clicking refresh while a download is still in progress; overlapping requests can make it harder to tell which result is current.
After refreshing, verify that the profile remains selected and that it loaded successfully. Look for a completion indicator, a recent update timestamp, or a profile status without an error. If the application shows a configuration validation message, read it before proceeding. A profile that appears in the list may still fail to load if its YAML structure is invalid, a required field is missing, or the current core cannot interpret an option used by the provider.
Automatic update intervals, when available, control how often the client checks for changes; they do not usually mean that every node is continuously tested. A manual refresh is useful after a provider announces a change or when expected nodes are missing. If an automatic update fails, the last successfully downloaded configuration may remain available, but do not assume that it has been updated. Check the displayed time and status so you know which configuration you are using.
Hands-On: Select a Node and Test It
With the profile loaded, use this sequence to move from an imported configuration to a verified connection. Exact button names and layout vary between Clash Verge Rev releases, but the underlying checks are the same.
- Open the proxy controls. Navigate to the page that lists proxy groups and their members. A profile may contain groups such as “Proxy,” “Auto,” “Fallback,” or a region-specific group. These are not necessarily individual servers; some groups contain other groups.
- Choose the group that handles general traffic. If you see a main group such as “Proxy” or “Global,” open it and inspect its available choices. A group called “DIRECT” sends traffic without a proxy, so selecting it will not test a proxy node.
- Select an individual node or an automatic group. For a straightforward first test, choose a node you recognize, or choose an automatic test group if the provider supplies one. An automatic group may select a node based on availability or latency; a manual selector lets you pick a specific entry yourself.
- Wait for the selection to take effect. Give the interface a moment to update. Confirm that the chosen node or group is shown as active. A successful latency test is useful, but it only indicates that a test request reached its destination; it does not prove that every application is routed through that selection.
- Enable the intended traffic mode. Turn on the system proxy if you want supported desktop applications to use Clash’s local proxy ports. If you need broader capture of application traffic, configure TUN mode where supported and grant any operating-system permissions it requests. These modes solve different routing needs and may require different permissions.
- Check the connection from an application. Open a website or service that should use the proxy, then observe the client’s traffic or connection view if available. Confirm that a connection appears and that its route uses the expected group or node rather than DIRECT.
Use a simple, repeatable test rather than changing several settings at once. For example, select one known node, make one request from a browser that honors the system proxy, and check the client’s connection list. If the request works, you have verified the profile, selection, and at least one routing path. You can then test other applications or enable TUN mode if those applications do not follow the system proxy.
The system proxy toggle does not force every program to use Clash. Some command-line tools, games, and applications have their own proxy settings or ignore the operating-system proxy. Conversely, TUN mode can capture traffic that would otherwise bypass the system proxy, but it may require administrator permission and can interact with VPN software, endpoint security tools, or existing virtual network adapters. Enable only the mode you need and test again after changing it.
Understand Nodes and Proxy Groups
A profile can present dozens of entries, and the labels are not always self-explanatory. A country or city name is a useful hint, not a guarantee of actual physical location or performance. The provider controls the names and server infrastructure. Latency tests also measure only the path to a particular test endpoint at a particular moment; they do not directly measure streaming quality, peak throughput, or reliability over a full session.
| Entry type | What it does | When to choose it |
|---|---|---|
| Individual node | Connects through one specific proxy endpoint. | Useful for a direct, easy-to-understand test or when you need a particular region. |
| Manual selector | Lets you select one of its listed nodes or nested groups. | Useful when you want control and expect to switch choices yourself. |
| URL-test group | Tests its members against a configured URL and can select a low-latency option. | Useful when you prefer automatic selection and the provider has configured the group appropriately. |
| Fallback group | Uses an available member according to the group’s configured order and health checks. | Useful when maintaining a primary choice with an available backup matters more than picking the lowest latency. |
| DIRECT | Sends matching traffic directly rather than through a proxy. | Useful for local or explicitly direct traffic, but not for verifying a proxied connection. |
For a first connection, a manually selected node makes troubleshooting easier because it removes automatic group behavior from the test. Once the basic route works, you can try the provider’s automatic group and compare results. If you choose an automatic group but see no active node, check whether the profile finished loading, whether the group contains available members, and whether its test URL is reachable from your current network.
Rules determine which group handles a request. Selecting a node in the main proxy group will not necessarily route every destination through it: a rule may send local addresses, a particular service, or a domain category to DIRECT or to another group. When a test behaves unexpectedly, inspect the connection’s matched rule and selected outbound group rather than assuming that the node selection itself is broken. For an initial check, use a destination that the profile is expected to proxy.
Verify That the Connection Is Active
There are three useful layers of confirmation. First, confirm that the profile is loaded without an error. Second, confirm that a node or group is selected and that the core is running. Third, generate real traffic and check the result in an application or the client’s connection view. A green status icon or a successful delay test alone is not enough: the client might be running while the selected group is DIRECT, the application might bypass the system proxy, or a rule might route that destination elsewhere.
For a practical test, choose a node, enable the relevant mode, and open a new page in a browser. If the browser was already open, try a new private window or a fresh connection because existing sessions can continue using a route established before the change. Check whether the client records the new request. If the request appears, inspect its rule, outbound group, and destination. This helps distinguish a routing decision from a connection failure.
- Profile check: The subscription is present, updated, and selected as the active profile.
- Core check: The Mihomo core is running, with no configuration or permission error.
- Selection check: The intended node or group is selected, not DIRECT or an unrelated group.
- Traffic check: A new request appears in the client and uses the expected route.
- Application check: The application is configured to use the system proxy, or TUN mode is active if the application does not honor it.
Keep the test narrow while diagnosing. If the profile, node, system proxy, TUN mode, DNS settings, and routing rules are all changed together, a successful result will not reveal which change fixed the problem. Return to one known profile and one known node, verify a single browser request, and then expand the setup only after that baseline is reliable.
Troubleshoot Common Setup Problems
The subscription will not download. Recheck that the full URL was copied correctly and that it is still active in the provider’s account portal. Confirm the computer’s date and time, because incorrect system time can interfere with secure HTTPS connections. Test access to the provider’s subscription host on the current network. If the link has expired or been reset, generate a new one with the provider and replace the old profile URL rather than repeatedly retrying an invalid link.
The profile downloads but shows an error. Record the exact error message and note which core and application release are being used. A malformed or incompatible provider response, an unsupported option, or a truncated download can prevent the configuration from loading. Refresh once after confirming network access. If the problem persists, ask the provider for a Mihomo-compatible subscription and send the error text with all secret URLs and tokens removed.
The node list is empty or incomplete. Refresh the active profile and check that the provider account is valid and has not reached a device or usage limit. Some providers deliver separate links for different client types, and a non-Clash link may not create the expected proxy entries. If the profile contains groups but no visible servers, inspect the group members or ask the provider to confirm that the subscription includes node data.
A node test succeeds but websites do not load. A delay test may reach its test endpoint even when your browser is not using the proxy. Confirm the system proxy toggle or configure TUN mode as appropriate, then inspect the browser request in the client. Check the matched rule and ensure the destination is not routed through DIRECT. If the connection is routed correctly but still fails, try another provider node and check whether the provider reports a service outage.
Some applications work while others do not. This is often a difference in how applications handle proxy settings, not evidence that the subscription is partially loaded. A browser may honor the system proxy while a game or terminal utility does not. Use that application’s own proxy configuration or evaluate TUN mode, taking care to follow operating-system permission prompts. If another VPN or network filter is active, test with only one traffic-capture tool enabled at a time.
The selected node changes back. You may have selected a node inside a group that is controlled by an automatic selector, or the active profile may have been switched. Return to the proxy page, inspect the group hierarchy, and select the desired entry in the group that actually handles the traffic. After a profile refresh, check the selection again because provider updates can change group membership or configuration.
Keep the Profile Reliable
Once the connection works, keep the profile management simple. Refresh when the provider changes its service or when a node disappears, and check the update result rather than assuming the refresh succeeded. Keep a note of which profile is intended for daily use if you have multiple subscriptions. If you remove a profile, remember that doing so may remove its locally saved configuration; make sure you still have access to the original provider link before deleting it.
When switching networks, such as moving from home Wi-Fi to a public hotspot, the selected node may no longer be reachable even though the profile remains valid. Try another node, then check the client’s connection information. Avoid importing untrusted configuration files to “repair” a subscription: profiles can contain routing and DNS settings as well as proxy endpoints. Use the provider’s official account page and support channel for replacement links or account-related changes.
A reliable setup is easy to summarize: keep the subscription URL private, load and activate the right profile, select a node or group, enable the traffic mode your applications need, and confirm the route with a fresh request. Once those checks pass, Clash Verge Rev is ready for normal use. If you still need the application, start with the official download page and then follow the setup guide for your operating system.