Tutorial September 9, 2026

Clash Verge Rev: How To Add Subscriptions And Use Nodes

Learn how to get started with Clash Verge Rev after installation. Follow clear steps to import a subscription URL, update your profile, choose a working node, turn on the proxy, and select the right operating mode.

Docker Proxy GitHub Acceleration Advanced Config YAML

1. Before you start: what a subscription actually provides

This guide is for users who have installed Clash Verge Rev but have not yet connected it to a usable proxy profile. The application itself is only the control panel. To make requests through remote servers, you still need a subscription URL, a local configuration file, or another Mihomo-compatible profile supplied by a provider or maintained by yourself. A subscription normally contains several parts at once: proxy server definitions, transport parameters, credentials, group names, and rule information. When you import it, Clash Verge Rev can display the available nodes and use the provider’s routing logic. You should therefore treat the URL as a private credential rather than as an ordinary web link.

Do not copy a subscription URL into a public issue, screenshot, browser bookmark shared with colleagues, or chat message. Anyone who obtains it may be able to retrieve your node list or consume the provider’s traffic allowance. If the URL includes a token, assume that token is equivalent to a password. When a provider offers a reset or renewal function, use it after accidental exposure.

Before opening Clash Verge Rev, confirm three basic details. First, check whether the provider gives you a complete profile or only a conversion link. Second, note whether the subscription is intended for Clash Meta, Mihomo, or another client format; recent Clash Verge Rev builds generally work best with Mihomo-compatible YAML or subscription output. Third, verify the device date and time. Incorrect system time can cause TLS certificates, subscription downloads, and authentication requests to fail even when the network itself is available.

You should also decide what success means. For most people, the first milestone is not maximum speed. It is a complete chain: the profile downloads, the configuration parses, a node responds, the system proxy is enabled, and a test website reflects the expected route. Once that baseline works, you can compare latency, change rules, and improve stability without guessing which layer caused the original failure.

2. Add a subscription URL in Clash Verge Rev

Open Clash Verge Rev and locate the page named Profiles, 订阅, or a similar profile-management section depending on the language and build. The labels may vary slightly between releases, but the workflow is usually the same: paste a remote URL, assign a readable name, then request an update. If you already see example profiles, do not edit them immediately. Creating a separate entry for your provider makes later troubleshooting much easier.

  1. Copy the complete subscription URL from your provider’s dashboard. Make sure the address starts with the expected protocol, such as https://, and that no characters were lost at either end.
  2. Return to the profile page and choose the control for adding a remote profile or subscription.
  3. Paste the URL into the address field. If the interface offers a name field, use a descriptive name such as Home Subscription or Work Travel Profile rather than leaving an automatically generated token as the title.
  4. Save the entry and click the refresh, update, or download button associated with that profile.
  5. Wait for the download and parsing process to finish. Do not repeatedly click update while the first request is still running.

A successful update usually changes the profile status from pending to available and displays a timestamp, file size, or node count. Click the profile once and inspect the preview if Clash Verge Rev provides one. You are looking for recognizable sections such as proxies, proxy groups, rules, and DNS settings. A page that shows a green download result but no usable proxies may indicate that the provider returned an unsupported format or an access page instead of a configuration file.

If the application reports a timeout, first test the URL in a normal browser. A browser error does not prove that the subscription is invalid; it may simply mean that the link requires a particular user agent, has expired, or is temporarily blocked. If the browser downloads a text file while Clash Verge Rev fails, compare the URL carefully and check whether the provider requires a conversion parameter. Avoid manually changing random query parameters because a seemingly small modification can remove required headers or format instructions.

Check the imported profile before activating it

An imported profile is not automatically the best profile for your device. Read its basic metadata, identify the available proxy groups, and check whether it contains a group intended for selection. Common group names include Proxy, Global, Auto, Fallback, or a provider-specific name. A group may contain dozens of nodes, while another group may contain only regional exits or streaming-optimized entries.

If the configuration shows a parsing error, do not try to solve it by deleting random lines. YAML depends on indentation, quoting, and special characters. A missing space can change the meaning of a complete section. Re-download the profile first, then confirm that Clash Verge Rev and the provider support the same configuration format. When the provider publishes a client-specific subscription link, use that link instead of a generic link intended for a different application.

3. Update and maintain the profile

Subscriptions are not static files. Providers may rotate server addresses, change credentials, remove overloaded nodes, or add new proxy groups. The profile saved in Clash Verge Rev is therefore a snapshot. Updating it periodically is important, but updating too often can also create confusion when you are trying to measure stability.

After the first successful import, open the profile’s context menu and look for an update interval or scheduled refresh option. A daily or several-times-per-week schedule is reasonable for many personal profiles. If your provider changes nodes frequently, a shorter interval may help; if the subscription is self-managed and rarely changes, manual updates are less disruptive. Keep in mind that some services count every retrieval against a quota.

When an update fails, distinguish between three different problems. A download failure means Clash Verge Rev could not retrieve the remote document. A parsing failure means it retrieved content but could not interpret it as a supported profile. A runtime failure means the profile loaded, but its nodes or rules do not work correctly. These problems require different fixes, so record the exact status message instead of treating every red icon as a dead proxy.

Keep one known-good profile available when possible. If a newly updated subscription suddenly breaks, switch back to the previous working version or export a backup before experimenting. Do not assume that the newest profile is always safer or faster. A provider may have changed a rule set, introduced a new DNS mode, or removed a group that your daily workflow depended on.

4. Choose a working node instead of guessing from its name

Once the profile is active, open the proxy or connections page. You may see a hierarchy rather than a flat node list: a top-level policy group points to an automatic group, and that group points to individual servers. To use a specific node, select the correct parent group first, then choose a child node. Changing a child node inside an unused group will have no visible effect on your browser.

Names such as “low latency,” “premium,” or “streaming” are useful hints but are not measurements. A node that looks fast in its label may be congested at the time you test it. Start with the application’s latency test if available, then open a real HTTPS page through the proxy. Latency checks often measure a small request to a fixed endpoint; they do not reveal whether a node can sustain downloads, long-lived connections, video playback, or large API responses.

Signal What it tells you What it does not guarantee
Latency How quickly a small test request receives a response Stable throughput or reliable streaming
Timeout The node or route failed to respond within the test period That every node in the same region is unusable
Download speed Approximate sustained transfer performance Good login, DNS, or WebSocket behavior
Connection log Which rule, group, and destination were actually used Whether the remote service permits the requested action

Test two or three candidates rather than selecting only the first green result. For each candidate, note the response time, whether the page loads completely, and whether repeated tests remain consistent. A node with slightly higher latency but no packet loss is often more useful than one with an excellent first result followed by frequent resets. If a service requires a particular region, choose a node in an appropriate region, but do not infer availability solely from the node’s label.

Use the connection panel to verify the destination. If you open a website and the log shows DIRECT when you expected a proxy group, the issue is probably a rule or mode selection rather than a dead node. If the log shows the expected proxy but the request fails, compare another node and inspect DNS or TLS errors. This simple distinction prevents many unnecessary subscription changes.

5. Turn on the proxy and select the right operating mode

Selecting a node does not always mean that other applications are using it. Clash Verge Rev normally exposes a system-proxy switch, a mode selector, and sometimes a TUN switch. These controls affect different traffic paths. The system proxy is commonly enough for browsers and applications that honor operating-system proxy settings. TUN mode captures traffic at a lower network layer and can cover applications that ignore those settings, but it also introduces more responsibility around DNS, routes, permissions, and exclusions.

Open the mode selector and understand the practical difference between the usual choices. Rule mode sends traffic according to the profile’s rules, allowing some domains to use a proxy while others remain direct. Global mode sends most eligible traffic through the selected proxy group, which is useful for diagnosis but may be inconvenient for local services, company resources, or domestic websites. Direct mode bypasses proxy routing and is useful as a control test, but it will not verify that the proxy itself works.

For normal daily use, rule mode is usually the best starting point. Enable the system proxy only after confirming that the intended profile is selected. Then open a fresh browser tab and test a simple HTTPS website. Some browsers retain connections created before the proxy was enabled, so a new tab or a full browser restart gives you a cleaner result. If an application still bypasses Clash, check whether it uses its own proxy settings, a sandbox, a separate network service, or QUIC traffic that your current setup does not capture.

Use TUN mode deliberately. It may help with command-line tools, launchers, games, or desktop software that ignores HTTP and SOCKS settings. However, TUN can change DNS behavior and route local traffic differently. Before enabling it, make a note of your original network state and ensure that Clash Verge Rev has the required administrator or system permissions. If local printers, corporate VPNs, or intranet services stop working, disable TUN temporarily and determine which route or DNS rule needs an exclusion.

A reliable test sequence is simple:

  1. Choose a known profile and confirm that it contains at least one node.
  2. Select a node or automatic group inside the active proxy group.
  3. Set the mode to rule mode for ordinary use, or global mode for a short diagnostic test.
  4. Enable the system proxy and verify that the switch remains enabled.
  5. Visit a test site and inspect the connection log for the destination and selected policy.
  6. Repeat the test with direct mode to establish a comparison point.

If direct mode works but proxy mode fails, focus on the node, proxy group, DNS, or provider route. If both modes fail, investigate the local application, browser, firewall, or upstream network before changing nodes. If the browser works but a terminal does not, configure the terminal explicitly when needed, for example with HTTP_PROXY and HTTPS_PROXY, using the local port shown in Clash Verge Rev. Do not assume that every command-line program reads those variables in the same way.

6. Troubleshoot common failures and build a repeatable routine

The most common beginner mistake is changing several variables at once. A user imports a new subscription, switches to global mode, enables TUN, changes DNS, and restarts the browser within two minutes. When the result is worse, there is no reliable clue about which change mattered. Instead, modify one layer at a time and record the result.

The subscription does not download

Check expiration, quota, URL spelling, and network reachability first. If the provider dashboard offers separate links for different clients, select the Mihomo or Clash-compatible option. A link that returns an HTML login page, a quota warning, or a JSON error may appear valid in a browser but cannot be parsed as a proxy profile. Corporate networks can also block subscription domains while allowing ordinary websites, so compare a home or mobile connection only when your network policy permits it.

The profile loads but every node fails

Test multiple nodes and inspect the connection log. If all nodes fail immediately, check the system clock, DNS resolution, firewall permissions, and whether the provider account is active. If only one region fails, the issue may be regional congestion or a provider-side outage. If latency succeeds but HTTPS pages time out, look for TLS, SNI, UDP, or DNS errors rather than repeatedly refreshing the same page.

The browser works but another application does not

That application may ignore system proxy settings. Check its own network preferences, environment variables, or launcher settings. Developer tools, package managers, and command-line clients often need explicit proxy configuration. A TUN setup can capture more traffic, but enabling it is not a universal fix: local routing conflicts, certificate validation, and UDP behavior can create new failures. Test the application with a single known destination before attempting a broad configuration change.

DNS and rule behavior look inconsistent

A domain may resolve differently under direct and proxied DNS, especially when fake-IP or enhanced modes are enabled. If a browser opens an old cached address while Clash sees a new one, clear the browser’s DNS cache or restart the browser after changing DNS behavior. Use the connection log to verify the actual rule. Put specific exceptions before broad catch-all rules, and keep local, work, and private network destinations on policies that match your organization’s requirements.

For routine maintenance, keep a short checklist: update the subscription, confirm that the profile parses, select a tested group, verify rule mode, enable the appropriate proxy switch, and inspect one or two real connections. Save a backup of important custom settings before replacing a profile. Most importantly, never upload a complete configuration that contains access tokens, private server details, or personal metadata when asking for support.

Compared with many one-click VPN clients that hide node selection, rule decisions, and application coverage behind a single switch, Clash Verge Rev exposes each layer you need to diagnose: subscription status, profile structure, proxy groups, connection logs, operating mode, and optional TUN capture. That transparency means there is a little more to learn, but it also lets you keep local services direct, move only selected traffic through a working node, and replace an unstable route without rebuilding your whole setup. If you want that level of control across Windows, macOS, Linux, and other supported environments, the next step is to choose the appropriate Clash client and continue with a clean profile setup.

Download Clash clients →

Ready to get started?

Install a compatible Clash client, import your subscription, and manage nodes with clear routing controls.