Clash Verge Rev Guide: Add Subscriptions and Switch Nodes

What You Need Before Starting

Clash Verge Rev is a desktop interface for the Clash Meta ecosystem. After installation, the application is ready to manage profiles, proxy groups, routing rules, connection logs, and system proxy settings, but it does not include working servers by itself. To connect to the internet through a proxy, you need a valid subscription URL from a proxy provider and a network connection that can reach that URL.

This distinction is important for new users. Installing the client only gives you the control panel; the subscription provides the configuration, proxy nodes, routing groups, and update information. A subscription may also be called a Clash configuration link, profile link, or subscription feed. It normally begins with https:// and contains a provider-specific path or token.

Use a subscription link intended for Clash, Clash Meta, or Mihomo when your provider offers several formats. Links labelled V2Ray, sing-box, Surge, Shadowrocket, or plain Shadowsocks may contain the same account information but are not necessarily formatted for Clash Verge Rev. If the provider offers a dedicated “Clash” or “Clash Meta” button, that is usually the safest choice.

Understand the Clash Verge Rev Interface

The exact labels can vary slightly between releases, but the main workflow remains consistent. The Profiles page is where you add and update subscription URLs. The Proxies page is where you select a policy group and choose an individual node. The Settings page contains system proxy, core, port, and application preferences. The connection or log view helps you confirm which rule and proxy group handled a request.

Several terms can be confusing at first. A profile is the downloaded YAML configuration that describes proxy servers, groups, rules, DNS behavior, and other settings. A proxy group is a selectable policy, such as “Proxy,” “Auto,” or “Fallback.” A node is one server entry inside that group. Selecting a profile does not automatically select a node, and selecting a node does not always enable the operating system proxy.

Before changing advanced DNS or rule settings, complete the basic profile and node workflow first. Most first-use problems come from an invalid URL, an inactive profile, a disabled system proxy, or a failed node—not from a missing custom rule.

Step 1: Add and Activate a Subscription

Open Clash Verge Rev and navigate to the Profiles section. You should see a field for a profile or subscription URL and an action such as Add, Import, Download, or Update. Copy the complete URL from your provider dashboard, paste it into the field, and submit it. Avoid typing the address manually because one missing character can produce a confusing download error.

1. Sign in to your proxy provider's dashboard.
2. Locate the subscription area and choose the Clash, Clash Meta, or Mihomo format.
3. Copy the full subscription URL, including any query string or token.
4. Return to Clash Verge Rev and open Profiles.
5. Paste the URL into the subscription field and click the download or add button.
6. Wait for the profile to finish downloading, then click the profile to activate it.

After a successful download, the profile usually displays its name, update time, and traffic or expiry information if the provider exposes those fields. If the profile appears in the list but is not highlighted as active, select it manually. The Proxies page may remain empty or show old groups until an actual profile has been activated.

When the download fails, first check the visible error message and the URL itself. Remove accidental spaces at the beginning or end, confirm that the address starts with https://, and test whether the subscription domain opens in a normal browser. A browser test is useful, but it does not prove that the returned content is valid Clash YAML. A provider may return an access-denied page, a rate-limit message, or a captive-portal notice instead of a profile.

Certificate errors can result from an incorrect system clock, an expired provider certificate, or a network that intercepts HTTPS traffic. Correct the computer's date and time, try another trusted network, and refresh the link from the provider dashboard. Avoid permanently disabling certificate verification simply to make an import work. A profile URL is sensitive, and accepting an untrusted connection can expose it.

Step 2: Refresh the Profile and Test Available Nodes

Subscriptions change over time. Providers may add servers, remove overloaded entries, rotate addresses, or update rule groups. The profile saved in Clash Verge Rev is a snapshot, so it should be refreshed periodically rather than treated as permanent. On the Profiles page, use the refresh or update action beside the active profile. Let the operation finish before switching to another page.

A refresh does not necessarily mean that the current node will change. It updates the configuration, but the selected proxy group may keep its previous choice or fall back to its first available entry. After every important update, open the Proxies page and confirm that the expected groups and nodes are present.

1. Open Profiles and identify the profile currently in use.
2. Click its refresh or update control.
3. Wait for the download and parsing process to complete.
4. Activate the refreshed profile if Clash Verge Rev creates a separate revision.
5. Open Proxies and expand the main proxy group.
6. Run the latency test if the interface provides a test button.

Latency results are helpful, but they are not a complete quality score. A node may respond quickly to an HTTP test and still perform poorly during video playback, large downloads, or long-lived connections. Conversely, a node with a slightly higher ping may be more stable during busy periods. Use latency as a filter, then evaluate real browsing behavior.

Do not repeatedly test dozens of nodes without observing the result. Begin with two or three geographically reasonable choices. Record which ones load normal websites, which ones handle streaming or downloads, and which ones fail only on particular destinations. This gives you a practical shortlist instead of relying on a single number in the latency column.

Step 3: Switch Nodes and Turn On the Proxy

Once the profile is active and nodes are visible, open the Proxies page. You will often see several layers: a top-level policy group, one or more automatic groups, and individual servers underneath them. Click the group that handles ordinary proxy traffic, then select a node from the list. The selected entry should become visually highlighted.

Some profiles use an automatic group such as URL-Test, Fallback, or Load-Balance. In that situation, you may select the automatic group rather than a specific server. The group then chooses nodes according to its configured behavior. This is convenient, but manually choosing a node is better when you are diagnosing a failure or comparing regions.

1. Open Proxies and find the group used by your rules.
2. Expand the group to view the available servers.
3. Choose a node with a successful test and reasonable latency.
4. Open Settings and enable System Proxy.
5. Set the mode to Rule unless you specifically need Global.
6. Open a new browser tab and test a destination that should use the proxy.

Rule mode is normally the best starting point. It lets the profile decide whether a request should go directly or through a proxy. Local services can remain fast while matching traffic uses the selected node. Global mode sends nearly everything through the chosen proxy and can be useful for testing, but it may increase latency for local sites and consume more subscription traffic.

Enabling System Proxy affects applications that respect the operating system's proxy settings. Browsers and many desktop applications do, but some games, command-line tools, virtual machines, and security software may ignore them. If you need broader coverage, Clash Verge Rev may offer TUN mode through the selected core. Treat TUN mode as an advanced option: review its permissions, DNS behavior, and compatibility with other VPNs or virtual network adapters before enabling it.

For a quick verification, visit a site that normally requires the proxy and then inspect the Connections view. Look for the destination hostname, the matched rule, and the final outbound or proxy group. If the request shows DIRECT when you expected a proxy, check the profile's rule order or test in Global mode temporarily. If the request uses the intended group but still fails, switch nodes before changing rules.

Troubleshoot Common Problems

If no profile downloads, start with the subscription URL and network path. Confirm that the link has not expired, that your account still has available traffic, and that the provider has not issued a replacement domain. Try a mobile hotspot or another trusted connection to separate provider problems from local DNS or firewall problems.

If the profile downloads but no nodes appear, the returned content may not be a Clash configuration. It may be an HTML login page, an error response, or a format intended for another client. Ask the provider for a Clash Meta or Mihomo subscription specifically. Also check whether the profile parser reports an invalid YAML structure or an unsupported proxy protocol.

If nodes appear but every test times out, verify that another VPN, proxy application, or security product is not occupying the same ports. Restart Clash Verge Rev after disabling competing tools, then test one node again. Network-wide blocking can also affect all nodes, while an expired account can make every server look offline at once.

If browsing works in Rule mode but a particular application does not, determine whether that application uses system proxy settings. You may need TUN mode, an application-specific proxy setting, or a compatible rule. Do not enable several network interception tools simultaneously, because their DNS and routing behavior can conflict and make the failure difficult to identify.

• Refresh the profile when nodes disappear or provider information looks outdated.
• Keep one known-good node as a baseline for comparison.
• Use Rule mode for everyday traffic and Global mode only as a diagnostic test.
• Check the connection log before editing YAML or replacing every setting.
• Turn off unused VPN clients and competing proxy services.
• Keep the subscription URL private and regenerate it if it has been exposed.

Some alternative proxy clients make subscription management feel simple but provide limited visibility when a profile fails, hide the difference between a selected group and an active system proxy, or require separate tools for node testing and rule inspection. Clash Verge Rev brings profile updates, group-based node switching, latency checks, logs, and system proxy controls into one workflow. If you want a clearer way to import a subscription and manage servers, you can Download Clash for free and try it with a compatible provider profile.