Installed Clash Verge Rev but not sure what to do next? The application itself is only the control panel; you still need to import a subscription, download its profile, choose a usable node, and select how traffic should be routed. This guide explains the complete Clash Verge Rev subscription setup process for beginners, including how to add a subscription URL, refresh an expired profile, switch servers, test node latency, choose a proxy mode, and troubleshoot the most common connection problems.

Before you begin: you need a valid subscription URL from your proxy service. A subscription URL is usually a long HTTPS address that contains your account or profile information. Treat it like a password and do not publish it or share screenshots that reveal the complete URL.

How Clash Verge Rev Works

Clash Verge Rev separates proxy management into three layers: the application, the profile, and the proxy group. Understanding this structure makes the interface much easier to use.

  • The application: Clash Verge Rev runs the local Clash or Mihomo core and provides the graphical interface for controlling it.
  • The profile: A YAML configuration file containing server nodes, proxy groups, DNS settings, routing rules, and other preferences. A subscription normally generates or updates this profile automatically.
  • The proxy group: A collection of nodes or nested groups. The active group determines which server handles traffic.

When you add a subscription, Clash Verge Rev does not immediately create a working connection simply by saving the URL. It must first download the remote profile, parse the YAML content, start the core with that profile, and expose the nodes in the proxy management page. If any one of these steps fails, the application may appear installed and running while browser traffic still goes direct or fails completely.

The exact labels may differ slightly between Clash Verge Rev releases and between Clash and Mihomo cores. You may see pages named Profiles, Proxies, Settings, or Logs. The workflow remains broadly the same: import a profile, activate it, select a group, and enable the system proxy or TUN mode.

Add a Subscription URL

A subscription URL is the fastest way to import several nodes at once. Instead of entering server address, port, UUID, encryption method, and transport settings manually, Clash Verge Rev downloads a provider-generated configuration containing those details.

  1. Open Clash Verge Rev and go to the Profiles page.
  2. Locate the subscription or remote profile input field.
  3. Paste the complete subscription URL into the field.
  4. Click the button used to import, download, or add the profile.
  5. Wait for the download and parsing process to finish.
  6. Confirm that a new profile appears in the profile list.

Some providers give you a normal Clash subscription URL, while others provide a general subscription link that must be converted into Clash or Mihomo format. If the downloaded file contains unreadable text, a different client format, or an error message instead of YAML, the link may not be compatible with Clash Verge Rev. In that case, use the provider's format conversion option or request a Clash-compatible link.

After importing the profile, click it to make it active. A profile can exist in the list without being selected as the current configuration. Look for a check mark, highlight, activation button, or status indicator showing which profile is currently running.

Protect your subscription URL: anyone who obtains the link may be able to retrieve your node configuration or consume your subscription traffic. Do not paste it into public issue trackers, chat rooms, or online debugging tools. If you accidentally expose it, reset or regenerate the subscription link from your provider account.

Check the Imported Profile

Before testing a node, inspect the profile status. A successfully imported profile should usually show a recent update time, a valid YAML or Mihomo configuration status, and a non-zero number of proxies. If the profile shows zero nodes, an empty proxy list, or a parsing error, activating it will not solve the problem.

Typical causes include an expired account, a subscription quota limit, an incorrectly copied URL, a provider outage, or a profile that uses features unsupported by the selected core. Copying the URL again is worthwhile, especially when it was copied from a mobile app where the address may have been truncated. Also check whether the provider requires an access token, user agent, or special conversion parameter.

Refresh and Update the Profile

Subscriptions are remote resources, so the node list and configuration can change after the initial import. A server may be removed, renamed, or replaced without any change on your computer. Refreshing the profile downloads the latest version and is the first step when a previously working node stops connecting.

On the Profiles page, find the imported subscription and use its refresh, update, or reload action. Some versions display a circular-arrow icon; others provide a context menu after right-clicking the profile. Wait until the operation completes instead of immediately switching pages. A large profile can take several seconds to download and parse.

After an update, verify these points:

  • The profile's update time has changed.
  • The number of proxies is reasonable and not unexpectedly zero.
  • The active profile remains selected.
  • Your custom settings have not been overwritten.
  • The Proxies page displays the expected proxy groups and nodes.

There is an important difference between a profile update and a core restart. Updating downloads new configuration data; restarting reloads the running core. If the profile was updated successfully but the old node list remains visible, activate the updated profile again or restart the core from the tray menu. Avoid repeatedly importing the same URL as separate profiles, because this creates duplicates and makes future maintenance confusing.

Subscription Update Best Practices

For everyday use, updating once or twice a day is usually enough unless your provider publishes frequent changes. Very short update intervals can waste bandwidth and may cause a provider to temporarily rate-limit your account. If Clash Verge Rev supports automatic update intervals, choose a moderate schedule and perform a manual refresh only when necessary.

Keep one known-good profile as a backup if your provider offers more than one configuration. However, do not assume that an old profile will remain valid forever. Credentials, server certificates, and subscription permissions can expire even when the local file is still present.

Switch Nodes and Test Latency

Once a profile is active, open the Proxies page. You will usually see a primary group such as Proxy, Proxy Group, or a provider-specific name. Selecting a node inside this group changes the route used by connections that match the proxy rules.

  1. Open the Proxies page.
  2. Find the group used by the general proxy rules.
  3. Expand the group if it contains nested groups.
  4. Click a node to make it active.
  5. Wait briefly for the selection indicator to update.
  6. Open the connection or log view if you want to confirm that new traffic is using the selected node.

Many clients display a delay value in milliseconds. Lower latency generally means faster response time, but it does not guarantee higher download speed. A node with a 90 ms test result may download faster than a node with 50 ms if it has better bandwidth, less congestion, or a more efficient route to the destination.

Use latency testing as a filter rather than the only decision criterion. First remove nodes that time out or show extremely high delay. Then compare several remaining nodes by opening the websites and services you actually use. A server that is excellent for video may not be the best choice for software downloads, gaming, or international websites.

What you see Likely meaning Recommended action
Low and stable delay The node responds consistently to the test endpoint Use it as a candidate for daily browsing
Timeout The node or route is unreachable Try another node and refresh the profile
Low delay but slow pages Bandwidth, destination routing, or congestion may be poor Test a different region or protocol
Delay changes significantly The route is unstable or overloaded Use another node or an automatic test group

Choose the Right Proxy Mode

Clash Verge Rev normally offers several modes that control how rules are applied. The best option depends on whether you want selective routing, a full tunnel, or a quick way to diagnose configuration problems.

  • Rule mode: traffic is matched against the profile's rules. Proxy services and selected domains use the active proxy group, while local, private, or explicitly direct destinations bypass it. This is the best starting point for most users.
  • Global mode: nearly all traffic is sent through the proxy group. It is useful for testing whether a node works, but it may send local services, domestic websites, or large downloads through the proxy unnecessarily.
  • Direct mode: Clash remains available, but traffic is sent directly. Use this to verify whether a problem is caused by the proxy configuration or by the local network itself.

Start with Rule mode. Then ensure the system proxy is enabled from the main window or tray menu. On Windows and macOS, this usually changes the operating system's HTTP and HTTPS proxy settings. Applications that respect system proxy settings will begin using Clash automatically, while applications with their own network settings may require manual configuration.

Rule mode does not necessarily capture every application. Command-line tools, games, virtual machines, and applications that ignore system proxy variables may continue to connect directly. For broader coverage, enable TUN mode if your Clash Verge Rev and operating system support it. TUN mode creates a virtual network interface and allows the core to process traffic that would not normally use the system proxy.

A practical testing sequence: use Global mode briefly to test a node, return to Rule mode for daily browsing, and use Direct mode when comparing the proxy route with your normal network. Do not leave Global mode enabled permanently without checking whether local services still work properly.

Verify That the Connection Works

Do not rely only on the green running indicator. A running Clash core means the local service started; it does not prove that the selected node can reach every destination. Verify the connection in layers.

  1. Confirm that the core status is running and that the selected profile is active.
  2. Confirm that the system proxy or TUN mode is enabled.
  3. Open a normal website that should be accessed directly.
  4. Open a service that should match a proxy rule.
  5. Check the connection panel to see whether requests are assigned to the intended group.
  6. Review the logs if a request fails, paying attention to DNS errors, connection timeouts, and TLS messages.

If a browser works but another application does not, the issue may be proxy support rather than node availability. Check that application's proxy settings, or use TUN mode when appropriate. If every application fails, first switch to another node, then try Direct mode. If Direct mode works but Rule and Global modes fail, investigate the subscription, DNS configuration, selected group, and core logs.

Common Problems and Practical Fixes

The Profile Download Fails

Check the subscription URL in a private location and make sure it begins with the correct protocol, usually https://. A URL copied with a missing character, trailing space, or line break may fail. If the URL is correct, the provider may be blocking requests from your current network or the subscription may have expired. Try the provider's account page to confirm its status, then update or regenerate the link if available.

The Profile Loads but Nodes Are Missing

This usually indicates a format or parsing problem. Confirm that the profile is intended for Clash or Mihomo rather than another client. Check the application logs for an invalid YAML key, unsupported proxy type, or failed provider conversion. Updating Clash Verge Rev may add support for newer Mihomo configuration fields, but you should not blindly edit a provider-managed profile without keeping a backup.

The Node Connects but Websites Fail

Test another node first. If all nodes show the same behavior, inspect DNS settings and routing rules. DNS failures can appear as ordinary website timeouts. A restrictive network may also block one transport or port while allowing another. Try a node from a different region or with a different protocol, and compare the result in the logs.

The Core Runs but the Browser Uses Direct Access

Make sure the system proxy switch is enabled and that no other proxy application is overwriting the operating system settings. Browser extensions can also replace or bypass system proxy settings. Temporarily disable competing proxy tools, restart the browser, and check the connection panel in Clash Verge Rev. For applications that ignore system settings, configure a local proxy manually or enable TUN mode.

Frequently Asked Questions

Is it safe to share a Clash subscription URL?

No. A subscription URL commonly contains an account token and may grant access to your complete server list. Keep it private, store it in a password manager if necessary, and regenerate it through your provider if it becomes public.

How do I find the best node?

Start by removing timed-out nodes, then compare stable candidates using both latency and real-world performance. Test the websites and services you use most often. The lowest ping is not always the fastest node because throughput, congestion, routing, and server load also matter.

Should I use Rule mode or Global mode?

Use Rule mode for normal daily browsing because it applies the profile's routing decisions and avoids sending every connection through the proxy. Use Global mode temporarily for testing or when you specifically need all supported traffic to use the selected node.

How often should I refresh the subscription?

Once or twice per day is sufficient for most users. Refresh it immediately when nodes disappear, a provider announces changes, or a previously working profile stops connecting. Excessive refreshes may waste bandwidth or trigger provider-side limits.

After the initial setup, Clash Verge Rev should require very little maintenance: keep the profile updated, choose a stable node, and leave Rule mode enabled for ordinary use. When something breaks, test the problem systematically by checking the active profile, selected group, system proxy or TUN status, node availability, DNS behavior, and logs in that order. This approach is faster and more reliable than repeatedly importing the same subscription or changing random settings.

Get Started

Take Full Control of Your Traffic with Clash

Available on Windows, macOS, Linux, Android, and iOS. Flexible rules, simple setup, ready to use.

Download Free View Setup Guide →