Clash Verge Rev Subscription Setup: Add Profiles and Switch Nodes

Installing Clash Verge Rev is only the first step. To use it, you need a profile containing your proxy nodes and routing rules, then you need to select a node and make sure traffic is reaching the app. This guide walks through the full Clash Verge Rev subscription setup: importing a subscription, refreshing it, choosing a proxy node, and checking common connection problems. Menu names can vary slightly between releases, but the workflow is similar across current versions.

Before You Import a Subscription

A subscription is a URL supplied by your proxy service. Clash Verge Rev uses it to download a profile, which typically includes node information, proxy groups, and routing rules. The URL is not just an ordinary web link: anyone who obtains it may be able to access or refresh your profile, depending on how the provider manages subscriptions. Treat it like a password.

Before importing, check that you have the subscription URL rather than a website login address or a single-node link. A provider may show a button labeled “Clash,” “Mihomo,” “Copy subscription,” or “Subscription URL.” If there are several formats, use the format recommended for Clash Verge Rev or Mihomo. If the provider supplies a dedicated configuration file instead of a URL, download that file and use the local-file import option.

Confirm the profile format: A Clash-compatible profile is usually YAML-based and may have a .yaml or .yml extension, though subscription URLs do not always show a file extension.
Check your account status: Expired plans, exhausted traffic, or an inactive subscription can prevent a profile from downloading or leave it with no usable nodes.
Use a trusted network: If the subscription request fails on a restricted network, try another connection before changing app settings.
Keep the URL private: Avoid posting it in screenshots, support forums, or public issue reports. Redact it before sharing logs.

Protect your subscription: Do not paste a private subscription URL into a public converter or an unfamiliar online tool. If you think the URL has been exposed, use your provider’s account page to reset or regenerate it when that option is available.

Add a Subscription Profile

In Clash Verge Rev, profiles are managed separately from the proxy nodes they contain. Importing a subscription creates a profile entry; selecting that profile makes its configuration active. You may be able to keep more than one profile in the list, which is useful when you have separate work, personal, or backup subscriptions.

Open Clash Verge Rev and go to the Profiles page. Depending on the release, this may appear in the sidebar as “Profiles” or “订阅.”
Choose the option to add a profile by URL. If you have a downloaded configuration file, choose the local-file option instead.
Paste the complete subscription URL into the address field. Check that it has no leading or trailing spaces and that it begins with the scheme supplied by your provider, usually https://.
Give the profile a recognizable name, such as the provider name or “Travel subscription.” A clear name helps when several profiles are stored in the app.
Save or confirm the entry, then wait for the download and profile parsing to finish. Do not close the app while the request is still in progress.
Once the profile appears in the list, activate it using the selection control associated with that profile. A profile that is merely present in the list is not necessarily the active configuration.

After activation, check that the profile shows a recent update time and that the app has loaded its configuration. The profile name alone does not prove that the subscription worked: a response could be an error page, an expired-account notice, or an empty configuration. If the app reports a parse error, verify that you copied the provider’s Clash-compatible URL and not a browser page or a URL intended for a different client.

When importing a local file, keep the original somewhere safe before making edits. A provider may overwrite the profile when it is refreshed, so direct changes to a remotely managed configuration can disappear. If you need persistent custom routing, use the app’s supported merge or override features rather than editing a downloaded subscription without understanding how updates are applied.

Refresh and Manage the Profile

A profile does not always update itself immediately after nodes change on the provider’s side. Use the profile’s refresh or update control to fetch the current version. In many builds, the control appears as a circular-arrow icon or in a profile’s context menu. Some versions also offer an automatic update interval; use the provider’s guidance if one is specified rather than refreshing repeatedly.

Refresh the profile when your provider adds or removes nodes, changes server details, or tells you to update your subscription. After the request completes, check the profile’s update status and open the proxy page again. If a refresh fails, the previously downloaded configuration may remain active; a failed update does not necessarily mean the current profile has been deleted.

What you see	Likely explanation	What to check
Profile refresh succeeds, but nodes look unchanged	The provider has not changed the configuration, or the app still has another profile active.	Confirm the active profile and compare its update time with the provider’s notice.
Refresh times out	The subscription host is unreachable, the network blocks the request, or the URL is no longer valid.	Check the network, confirm the URL in the provider account, and retry once.
Profile parsing fails	The response is not a valid supported configuration, or the provider returned an error page.	Confirm the selected subscription format and ask the provider whether the URL is active.
Profile loads but contains no nodes	The account may be expired, out of allowance, or configured with a different output format.	Check account status and request the correct Clash/Mihomo subscription link.

If the provider allows you to reset a subscription URL, do so only when necessary. Resetting it may invalidate the old URL on your other devices, which will then need to be updated as well. Keep a note of which devices use each profile, but store the actual URL in a secure location rather than in an unprotected document.

Choose a Proxy Node and Test It

With the correct profile active, open the Proxies page. Profiles often define proxy groups such as “Select,” “Global,” “Auto,” “Fallback,” or a group named for a service or region. A group is a selector or policy; the node you want may be one level inside it. If you only see group names, open the group to view its available choices.

Find the main proxy group used by the configuration. If the profile has a group named “Proxy,” “GLOBAL,” or “Select,” start there.
Choose an individual node, or select an automatic group if the provider has supplied one. An automatic group may run latency checks and choose a node for you.
Use the delay-test control, if available, to compare candidate nodes. A lower delay can make a connection feel more responsive, but it does not guarantee higher download speed or access to every service.
Wait for the selection to update. If the interface shows a selected node or a check mark, confirm that it is the node you intended to use.
Open a site or app that should follow the proxy rules. Then check the app’s traffic or connection view to confirm that a connection is being handled by the expected group.

There are two common ways to select: choose a specific node manually, or choose an automatic proxy group that makes a selection based on health checks. Manual selection is useful when you need a particular region or want predictable behavior. Automatic selection is convenient, but its test URL, interval, and group design come from the profile, so the “fastest” result may not be the best choice for every destination.

Also check the app’s operating mode. In Rule mode, the configuration decides whether each connection is direct or proxied; selecting a node does not force every app or website to use it. Global mode sends traffic through the selected proxy group more broadly, while Direct mode bypasses the proxy. Mode labels and behavior can depend on the loaded configuration, so use Rule mode for normal rule-based routing unless you are deliberately testing another mode.

Test one thing at a time: First confirm that the profile is active, then select a node, then test a destination. Changing the profile, mode, node, and system settings together makes it much harder to identify what fixed—or caused—the problem.

Check System Proxy and TUN Settings

Choosing a proxy node does not by itself guarantee that every application will use Clash Verge Rev. The client must receive the traffic, and that depends on how traffic capture is configured. For browser traffic, the system proxy option is often sufficient. Applications that ignore the operating system’s proxy settings may need TUN mode or their own proxy configuration.

Enable the system proxy from the main window when you want supported desktop applications to follow the operating system’s proxy settings. If a browser still connects directly, check whether it uses a separate proxy extension, custom proxy settings, or a profile that bypasses the system proxy. Avoid running several proxy clients that all try to control the system proxy at the same time.

TUN mode creates a virtual network interface and can capture more traffic than the system proxy, including traffic from some applications that do not honor system proxy settings. It may require administrator permission, a compatible core, and additional network configuration. Enable it only when you need that broader capture, and disable it temporarily when diagnosing conflicts with VPN software, security tools, or another virtual network adapter.

Use the following checks before concluding that a node is broken:

Confirm the active profile and the selected node or proxy group.
Check whether the mode is Rule, Global, or Direct and whether that mode fits the test.
Verify that the system proxy is enabled, or that TUN is running if the application requires it.
Try a browser that uses the operating system proxy and compare it with the affected application.
Look at the connection or traffic view to see whether requests appear and which rule or group handles them.

Troubleshoot Common Subscription Problems

When a page will not load, separate the problem into three stages: subscription retrieval, node connectivity, and traffic routing. A problem at the first stage prevents the profile from being updated. A problem at the second means the selected server cannot be reached or does not pass its test. A problem at the third means traffic is not being captured or the rules are sending it somewhere unexpected.

Symptom	Possible cause	Practical next step
Subscription URL cannot be fetched	Incorrect URL, expired account, DNS issue, or blocked access to the subscription host.	Copy the URL again from the provider account, check account status, and test the request on another network.
All node tests time out	Network restrictions, an outdated profile, or a temporary provider-side outage.	Refresh once, test another network, and check the provider’s service status before changing advanced settings.
Some nodes work while others fail	A particular server may be offline, overloaded, or unavailable from your current network.	Select a different node and compare results. Report the failing node name to the provider without sharing your subscription URL.
Delay test succeeds, but websites do not load	A delay test checks only a specific endpoint; it does not prove that all destinations are reachable.	Check the mode, system proxy or TUN status, and the rule or group handling the destination.
One app works but another does not	The second app may ignore system proxy settings or use its own DNS, VPN, or network stack.	Test with a supported browser, review the app’s proxy settings, and consider TUN only if appropriate.
Connection works, but a service still shows the wrong region	The service may use a different connection path, cached data, or location signals beyond the proxy IP.	Confirm the request appears in Clash, check the selected exit location, and clear the service’s relevant session data.

Change only one setting between tests and allow the result to settle. If you switch modes, nodes, DNS options, and TUN settings at the same time, a successful test will not tell you which change mattered. Restarting the entire app is not the first remedy for every issue; first verify the active profile, current selection, and whether requests are visible in the connection view.

If you contact your provider, include the client version, operating system, approximate time of the failure, profile update status, and the names of the affected nodes. Do not include the full subscription URL, account credentials, private keys, or unredacted configuration secrets. These details help support staff distinguish an account or server issue from a local routing problem while keeping your subscription protected.

Keep Your Setup Reliable

A dependable setup is usually simple: keep one clearly named active profile, refresh it when needed, use a suitable proxy group, and confirm that the traffic-capture method matches the applications you use. Remove old profiles only after checking that no device or workflow still depends on them. If a provider changes its subscription URL, update each device deliberately instead of assuming that an old profile will continue to refresh.

For everyday use, start with Rule mode and the provider’s recommended proxy group. If a particular site fails, inspect its connection and routing result before switching everything to Global mode. If no traffic appears in Clash, focus on system proxy or TUN capture; if traffic appears but the connection fails, compare nodes and verify the profile. This step-by-step approach makes subscription setup easier to maintain and gives you a clearer report if you need help from your provider.