Clash Verge Rev Setup Guide: Add Subscriptions and Switch Nodes

Getting Started with Clash Verge Rev

Clash Verge Rev is a desktop client for managing proxy profiles and routing network traffic through a compatible core such as Mihomo. The application provides the interface, but it does not automatically supply proxy servers or a subscription. You need a configuration from a provider or another trusted source before you can select a node and connect.

This guide covers the routine setup after installation: adding a subscription, refreshing its configuration, testing and selecting a proxy node, and checking that the system proxy is enabled. The exact wording and placement of controls can vary between Clash Verge Rev releases and operating systems, so use the steps as a workflow rather than relying on a particular button position.

It also helps to distinguish three settings that are easy to confuse. A profile contains the servers, groups, and rules supplied by a configuration. A node is an individual proxy server, often selected through a group in the client. The system proxy setting tells supported applications to send traffic through Clash Verge Rev. Adding a profile alone does not guarantee that traffic is being proxied.

1Add a Subscription or Profile

A subscription is usually a URL that the client uses to retrieve a configuration. Your provider may display it as a subscription link, import link, or Clash-compatible URL. Some providers instead offer a configuration file for download. Use a link or file intended for Clash or Mihomo; a link designed for a different client may not contain a format this profile manager can read.

If you were given a file instead of a URL, choose the local-file import option and select the configuration file from your device. Keep the original file unchanged until you have confirmed that the imported profile works. If you must edit YAML manually, preserve indentation: YAML uses spaces to define structure, and even one misplaced line can cause a parse error.

A newly imported profile may contain several proxy groups rather than a single server list. Groups can be named by region, use case, or selection method. This is normal: a group may let you choose a node manually, automatically select one, or balance requests across several available nodes. The profile is the overall configuration; the group is where you usually make a practical routing choice.

2Refresh the Profile and Check Its Status

Subscriptions are often updated to add servers, remove unavailable nodes, or change routing rules. When your provider publishes an update, refresh the profile in Clash Verge Rev rather than importing the same link repeatedly. Find the profile in the profiles list and use its refresh, update, or download action. Wait for completion before switching profiles or closing the application.

After refreshing, check the status message and the profile's last-updated time if the interface displays one. Then open the proxy or connections area and see whether the expected groups and nodes are present. A successful download does not prove that every server is reachable, but it does confirm that the client received and parsed the profile.

• Update succeeds and nodes appear: Continue to group and node selection. A provider may still have some temporarily unavailable servers.
• Update succeeds but the list looks unchanged: The provider may not have changed the configuration, or the profile may update in place without changing its display name. Check the update time and provider status before assuming the import failed.
• Update fails immediately: Verify that the URL is complete, current, and copied from the correct account. Check whether the provider has reset the link or requires a different subscription format.
• Update times out: Check your internet connection and retry after a short pause. If other websites work but the subscription host does not, the host may be temporarily unavailable or inaccessible from your current network.

When a URL import fails, use this sequence to narrow down the cause:

1. Copy the subscription URL from the provider's account page again. Do not reuse a shortened, truncated, or browser-formatted address.
2. Check whether the provider requires an account login, a specific user agent, or a particular client type for subscription downloads.
3. Confirm that the device clock and network are working normally, then retry the update. Certificate validation and timeouts can be affected by incorrect system time or unstable connectivity.
4. Look at the client log or error detail. A YAML parsing message points to a configuration-format problem; an HTTP status or timeout points more toward the request or server.
5. If the error persists, ask the provider whether the link is active and compatible with Clash Verge Rev or Mihomo. Share the error text, not the private subscription URL.

3Find and Select a Working Proxy Node

Once the profile has loaded, open the proxy or routing view. Many configurations organize nodes under groups such as regional lists, automatic selection, or a general proxy group. Select the group that handles the traffic you want to test, then choose a node inside it if the group supports manual selection. Some profiles use an automatic group, in which case the client or configuration chooses a node for you.

Do not assume that the first node is the fastest or that a region label guarantees a particular level of performance. Actual results depend on the server's current load, the route between your network and that server, the service you are accessing, and the behavior of the configuration's rules. A node that is responsive for one destination may not be the best choice for another.

1. Start with a node or group recommended by your provider, or choose a nearby region if the provider gives no guidance.
2. If the client offers a delay test, run it and allow the results to finish. Treat the number as a rough comparison, not a guarantee of real-world speed or reliability.
3. Select a candidate node and wait for the selection to take effect. Confirm that the group shows the intended choice rather than a different automatic selection.
4. Open a simple website or application that should follow the proxy rules. If the profile is rule-based, not all traffic will necessarily use the selected node.
5. If the connection fails, try another node in the same group. Testing two or three candidates can help distinguish a single-server problem from a broader configuration or system-proxy issue.

Keep the test consistent when comparing servers. Use the same destination and connection type, and avoid starting large downloads or video streams during a delay test. If one node has a slightly higher test result but loads the services you need more reliably, it may be the better everyday choice. Stability and usable throughput matter more than a single low-latency number.

Understand Groups and Rules

A group can represent a manual selector, an automatic test group, a load-balancing group, or another policy defined by the profile. The names and behavior are controlled by the configuration, not necessarily by Clash Verge Rev itself. If selecting a node in one group does not change an application's route, the profile's rules may send that traffic through a different group or directly to the internet.

For a first test, use the configuration's main proxy group if it is clearly identified. Avoid editing rules just to force one application through a server until you understand the profile's routing logic. Changing rules can affect many destinations and may make a working configuration difficult to restore. If you do make an edit, keep a backup and note what you changed.

4Enable the System Proxy and Verify Traffic

Choosing a proxy node and enabling the system proxy are separate actions. When the system proxy is enabled, applications that respect the operating system's proxy settings can send supported traffic through Clash Verge Rev. Some command-line tools, games, background services, or applications with their own network settings may ignore this setting. TUN mode is a separate routing option and may require additional permissions; it is not necessary for every basic browser test.

In Clash Verge Rev, locate the system-proxy control in the dashboard or settings. Turn it on, approve any operating-system permission prompt if one appears, and confirm that the control remains enabled. On Windows or macOS, another proxy application or a manually configured proxy can conflict with the setting. If the control will not stay on, close competing network tools and review the client log before changing unrelated system settings.

If the browser works but another application does not, that application may not use the system proxy. Check whether it has its own proxy settings, whether the profile's rules route its traffic directly, and whether the client supports the traffic type it uses. If no application connects, try a different node and inspect the log for connection, DNS, or configuration errors. Avoid changing several settings at once: make one adjustment, repeat the same test, and record the result.

Common Connection Checks

• Profile is loaded, but the browser still uses the direct route: Verify the system-proxy control and inspect the active rule for the destination. A rule-based profile may intentionally send some sites through DIRECT.
• The selected server shows a delay but pages do not load: A delay test only checks a specific endpoint. Try a different node, confirm the profile is active, and inspect the connection log for the actual destination.
• Only some websites fail: The issue may be a routing rule, DNS behavior, or a destination-specific restriction rather than a complete proxy failure. Compare a working and failing destination in the connections view.
• The client reports a configuration error: Refresh the provider profile and check the error detail. Avoid hand-editing provider-managed files unless you understand how updates may overwrite your changes.
• Nothing works after changing several options: Return to the last known-good profile and basic system-proxy setup, then test one variable at a time. This makes it easier to identify what caused the failure.

For everyday use, keep the profile updated when your provider recommends it, but do not refresh repeatedly when the service is working normally. If a specific node becomes unreliable, switch nodes before rebuilding the entire configuration. When you change a profile or system setting, verify the result with the same test you used before. This simple habit helps separate a server outage from a client setting, a routing rule, or a local network problem.

Download Clash for Free →