Adding a subscription to Clash Verge Rev is usually a short process, but a successful import does not automatically mean every proxy node is ready to use. You need a valid subscription URL, a profile that has finished downloading, and a node that can reach the destinations you care about. This walkthrough explains how to add and refresh a profile, compare nodes, and narrow down common import and connection problems. Menu names can vary slightly between releases, so if a label differs in your build, look for the equivalent profile, update, or proxy-group control.
Before You Add a Subscription
A subscription URL is a private link that lets the client download a configuration or a list of proxy nodes from your provider. Treat it like a password: anyone who obtains the link may be able to use your service or view subscription information. Do not paste it into public forums, screenshots, shared documents, or untrusted online converters. If you believe it has been exposed, check whether your provider lets you reset or regenerate it.
Before opening Clash Verge Rev, make sure you have the following:
- A current subscription URL: Copy it from your provider’s account page. A URL intended for a browser login or a single-node configuration is not necessarily a subscription link.
- A working internet connection: The app must be able to contact the subscription server before it can download the profile.
- A compatible core: The profile may use features supported by Mihomo but not by an older or different core. If the profile imports but reports configuration errors, check the core selected in the app and the provider’s supported clients.
- A little time for the first download: The initial request can take longer than a later refresh, particularly if the provider has many nodes or the connection to its server is slow.
It also helps to know the difference between a profile and a node. The profile is the downloaded configuration, which may contain many nodes, proxy groups, and routing rules. A node is one proxy endpoint inside that profile. Adding a profile makes its contents available; selecting a node determines which proxy a particular group will use.
Add the Subscription Profile
In Clash Verge Rev, open the Profiles view. Depending on the version, the action for creating a profile may be labeled New, Add, or shown as a plus button. Choose the option for a remote profile or subscription URL rather than selecting a local file. Paste the link into the URL field, give the profile a recognizable name, and confirm the import.
Use a name that will still make sense later. For example, a short provider name with a region or plan label is easier to identify than a generic name such as “New Profile.” The profile name is local to your client; it does not change the subscription contents or affect which nodes are available.
- Copy the subscription URL directly from your provider’s dashboard. Avoid adding spaces before or after it.
- Open Profiles and choose the option to add a remote profile.
- Paste the URL and enter a descriptive profile name if the dialog offers one.
- Save or confirm, then wait for the download and parsing process to finish.
- Check that the new profile appears in the list and that the app does not show an import or configuration error.
If the interface asks for a format or update interval, use the provider’s recommendation unless you have a specific reason to change it. Many subscriptions are already served in a format that Clash Verge Rev can detect. Avoid guessing at optional headers or conversion settings: an incorrect value can make a valid URL appear broken. If the app displays a profile preview or error details, read those before trying to add the same URL repeatedly.
After the profile downloads, select it as the active profile if it is not already active. Importing and activating are separate actions in some versions. A profile can be present in the list but not be the one currently controlling the running core. Look for a selected indicator or an explicit activate/use control, and make sure the core has loaded the profile successfully.
Refresh and Activate the Profile
A subscription profile is not necessarily a static file. Providers may change node addresses, credentials, availability, or routing rules. To fetch the latest version, open the profile’s action menu and choose its update or refresh command. Some versions also provide a refresh icon beside each profile. Wait for the operation to complete and check the result before assuming the new data was applied.
A successful refresh normally updates the contents of the existing profile; it should not require you to add the same URL as a second profile. If you deliberately add the URL again, you may end up with duplicate entries that are difficult to distinguish. If the refreshed profile still shows old information, verify that you updated the active entry and not another profile with a similar name.
Refresh frequency is a balance. Updating too often usually provides no benefit and may trigger provider-side rate limits. Updating only after a problem can leave you using a node that has already been replaced. If the client lets you configure an interval, follow the provider’s recommendation. Otherwise, use the manual refresh command when the provider announces changes or when you need to troubleshoot an outdated profile.
Once the profile is active, check the main controls that affect traffic. Depending on your setup, Clash Verge Rev may offer a system-proxy control and a TUN mode control. These are not the same as selecting a node. System proxy settings direct compatible applications through the local proxy, while TUN mode can capture more system traffic but may require additional permissions. For an initial test, keep your setup simple: confirm the profile is loaded, choose a node, and use the connection mode you normally rely on.
Choose and Test a Proxy Node
Open the Proxies view, or the equivalent proxy-group screen in your version. A profile commonly includes groups with names such as “Proxy,” “Auto,” “Select,” or a service-specific label. A group is a selection mechanism; it may contain individual nodes, other groups, or both. Choose a node in the group that actually handles the traffic you want to test. Selecting a node in an unrelated group may not change the route used by your browser.
Many clients provide a latency-test control, often shown as a small button or icon near a group or node. Run the test after the profile has finished loading. A displayed delay means the client received a response to its test request within that time. It is useful for comparing nodes under similar conditions, but it is not a complete measure of browsing quality. Results can vary with the test URL, the route to that endpoint, server load, and the time of day.
- Compare like with like: Test several nodes from the same profile using the same test control. A result from a different test endpoint may not be directly comparable.
- Look for consistency: A node that repeatedly responds with moderate latency may be a better everyday choice than one that occasionally shows a very low result but frequently times out.
- Check the destination you need: A latency test to one endpoint does not guarantee access to every site or service. Test an actual destination relevant to your use case after choosing a node.
- Confirm the selected group: If the profile has nested groups, make sure the top-level group and its underlying node both point to the route you intend to use.
For a manual selection group, click the node you want and allow the interface to update its selected state. For an automatic group, the client may choose a node based on tests or a fallback order; you may need to select a specific member only after opening the group. Avoid changing several groups at once during troubleshooting. Make one change, test the result, and then continue so you can identify which choice made a difference.
Hands-On Setup: From URL to a Working Node
Use this sequence for a first-time setup. It separates profile download problems from node-selection problems, making it easier to locate the point where something goes wrong.
- Add the remote profile. Paste the provider’s subscription URL into the remote-profile form, name the entry, and confirm. Wait until the download finishes rather than switching pages immediately.
- Check the import result. Confirm that the profile appears in the list and that there is no parse error. If the client reports a configuration problem, note the exact message and check whether the provider supports the core version selected in Clash Verge Rev.
- Activate the profile. Select the new profile and verify that the app or core indicates it has loaded. Do not assume that adding a profile automatically makes it active.
- Open the proxy groups. Find the group responsible for general proxy traffic. Expand it if necessary so you can see whether it contains individual nodes or another selection group.
- Run a latency check. Test a few available nodes and note which ones return results. A timeout is useful information, but it does not by itself prove that the entire profile is invalid.
- Select one node. Choose a responsive node in the relevant group. Keep other settings unchanged for this first test.
- Test real traffic. Open a destination that should use the proxy and verify that the request completes. If it does not, confirm that the application is using the system proxy or that your intended TUN setup is active.
- Record what worked. Note the profile name, the selected group, and whether latency testing or real traffic failed. This makes later refreshes and support requests more precise without exposing the private URL.
When the node is reachable but a particular website is not, the issue may be routing rather than node availability. A rule may send that domain directly, route it through a different group, or match a more specific policy. Conversely, a successful latency test does not prove that the application you are testing uses Clash Verge Rev at all. Check the active group and the traffic mode before replacing a node that may be working correctly.
Troubleshoot Import and Connection Problems
The Subscription URL Will Not Import
First verify that the link is complete and copied from the subscription section of your provider’s account. A login page, a browser-only redirect, or a URL that has lost characters during copying will not necessarily return a usable profile. Try opening the provider’s account page again and copying the link without editing it. Do not paste the secret URL into a public URL checker.
Next, check whether the subscription server is reachable from your current network. A temporary DNS issue, captive portal, firewall, or provider outage can interrupt the download. If the client provides a clear network error, compare it with a second attempt after confirming ordinary internet access. If the response downloads but parsing fails, the URL may be valid while the returned configuration uses a format or feature unsupported by the current core. In that case, check the provider’s client instructions and the core compatibility information rather than repeatedly importing the same profile.
Refresh Does Not Update the Profile
Confirm that you used the refresh action on the intended profile and that the request completed without an error. A provider may return unchanged contents when no nodes have changed, so an identical profile is not necessarily evidence that refresh failed. If the profile has an expiration or usage limit, check the provider dashboard for its status. When several entries have similar names, rename them locally so you can identify the profile you are updating.
A Node Times Out or Traffic Will Not Connect
Test more than one node before concluding that the subscription is unusable. One node may be offline while the others remain healthy. If every node times out, check that the profile is active, the core is running, and the device has internet access. A local firewall or security tool may also block the client’s core. On systems using TUN mode, confirm that the required permissions and network components are available; as a diagnostic step, compare with the ordinary system-proxy mode if that is suitable for your setup.
If latency tests succeed but real traffic fails, verify the selected proxy group and the route applied to the destination. Also make sure the application under test is using the proxy. Browser settings, system proxy support, and TUN routing can behave differently. Change one setting at a time and retest; switching nodes, modes, and rules simultaneously makes the cause much harder to find.
Frequently Asked Questions
Is a profile the same thing as a proxy node?
No. A profile is the configuration downloaded from a subscription, and it can contain multiple nodes, groups, and rules. A node is one proxy endpoint within that configuration. You add or refresh the profile first, then select a node through the appropriate proxy group.
Does importing a subscription automatically connect to a node?
Not always. Importing makes the profile available, but you may still need to activate it, start or reload the core, choose a node, and enable the traffic mode used by your apps. Some profiles define automatic groups, while others expect you to make a manual selection.
Should I always choose the node with the lowest latency?
Not necessarily. Latency tests measure a specific request to a specific endpoint at a particular moment. For daily use, stable connections and successful access to your intended destinations can matter more than the lowest single number. Compare several nodes and test real traffic before settling on one.
Can I share my subscription URL when asking for help?
Avoid sharing it. The URL may grant access to your subscription and should be treated as a credential. Share the non-sensitive error text, your Clash Verge Rev version, the selected core, and whether the failure happened during import, refresh, latency testing, or real traffic. Redact private credentials from screenshots and logs.
Once the profile is loaded and a node has passed both a basic latency check and a real-traffic test, save the working selection and refresh the profile only when needed or when your provider recommends it. If you still need the client or a broader configuration walkthrough, use the resources below and keep your subscription URL private throughout setup.
Take Full Control of Your Traffic with Clash
Available on Windows, macOS, Linux, Android, and iOS. Flexible rules, simple setup, ready to use.