Clash Verge Rev: How To Add Subscriptions And Switch Nodes

Understand the Clash Verge Rev Workflow in Depth

Clash Verge Rev is easier to use when you separate four different tasks that are often mixed together in beginner tutorials: importing a subscription, activating a profile, selecting a proxy group or node, and enabling the traffic mode that your applications can actually use.

A subscription is normally an HTTPS URL provided by your service provider. When Clash Verge Rev downloads that URL, it receives a configuration containing proxy servers, proxy groups, DNS settings, and routing rules.

The profile may include names such as PROXY, AUTO, Fallback, or a provider-specific group. A node is an individual server inside that configuration, while a proxy group is the menu that decides which node will be used. Choosing a node from a group is therefore different from changing the entire profile.

Mechanically:This distinction explains plenty common reports such as “Clash Verge Rev imported successfully but no websites load” or “I selected a fast server but the connection did not change.” The profile can be downloaded correctly while the wrong profile remains active; the node can be selected while the system proxy is still disabled; or browser traffic can work while a terminal or game bypasses the HTTP listener. A it holds up setup checks each layer in order instead of repeatedly replacing the subscription link.

Installing the application only everything includeds the first part of the journey. Until a valid profile is active and traffic is directed through the client, opening the dashboard does not prove that your connection is working.

Prepare the App and Subscription Before Importing Mechanically

Before opening the add dialog, confirm that you have a current Clash-compatible subscription reasonably than a website login URL, a single-node sharing link, or an obsolete format intended for another application. Providers may offer several export types, including Clash, Clash Meta, Mihomo, Surge, or sing-box.

It is also worth checking the computer clock. TLS validation can fail when the system date or time zone is substantially wrong, causing the subscription request to show a certificate exception or a generic network failure.

More strictly:On Windows, enable automatic time synchronization in Settings → Time & language → Date & time. On macOS, open System Settings → General → Date & Time and enable automatic date and time. A correct clock will not make an unavailable server work, but it removes one avoidable cause of failed adds.

Close other Clash-family clients while you configure Verge Rev. Clash for Windows, another Verge fork, Mihomo Party, and a system VPN may each install a helper, occupy the same mixed port, or create a competing TUN front-end.

Running two clients can produce confusing results: one dashboard shows a selected node while another process owns the system proxy, or DNS requests are sent through a different virtual adapter. Keep one primary client active during testing.

At a different level:Finally, decide whether you need only browser traffic or broader device coverage. System proxy mode is often sufficient for Chrome, Edge, Firefox, and plenty desktop applications that honor HTTP or SOCKS settings.

Terminal tools, games, virtual machines, container workloads, and applications with their own networking stack may need TUN mode or explicit proxy environment variables. This decision affects the permission prompts and troubleshooting steps later in the setup.

For Clash Verge Rev, choose the toggle that explicitly targets Clash Meta, Mihomo, or a current Clash YAML configuration when such choices are available. A legacy export may download without an exception but omit groups or transport settings that modern nodes require.

Add a Subscription in Clash Verge Rev Step by Step

The exact labels can differ slightly between Clash Verge Rev releases, but the general workflow remains not jumpy. The profile or subscription page normally contains an input field for a URL, an add button, and a list of downloaded configurations.

Thinking it through:If the add fails immediately, first copy the URL into a private browser window only to check whether the server responds with a download reasonably than a login page. Do not leave the URL in browser history on a shared computer.

1. Open the Profiles or Subscriptions page. Launch Clash Verge Rev and locate the page that lists local profiles and remote subscriptions. If the application opens on the dashboard, use the left navigation reasonably than changing proxy settings first.
2. Paste the provider URL. Copy the everything included HTTPS subscription link, including its query string, and place it into the subscription input field. Avoid adding spaces or line breaks at the beginning or end.
3. Kick off the download. Click Add, Add, or the equivalent download control. Wait for the request to finish; large subscriptions may take longer because the provider has to generate and compress plenty nodes.
4. Inspect the downloaded profile. Confirm that the result contains proxy groups and recognizable node names. A profile that contains only a blank entry, an HTML exception page, or a provider login message is not a usable Clash configuration.
5. Activate the profile. Click the profile card or its activation control so that Clash Verge Rev uses it as the current configuration. Downloading a profile does not by itself mean that it is active in every release.

A response containing YAML text or a file download is a useful sign; a web portal, CAPTCHA, 403 message, or expired-token notice points to a provider-side issue. You may also try a different network temporarily, because a local firewall, DNS filter, or captive hotel portal may block the subscription host even when ordinary websites open normally.

After the profile is active, open its details or editor view and look for the expected top-level sections. Most of of modern configurations include proxies, proxy-groups, and rules.

First, a clarification:You do not will want to edit those sections as a beginner. The important checks are that the file is not empty, the proxy group list is populated, and the configuration parser reports no syntax exception.

Do not paste the subscription into a proxy group field or into a YAML editor intended for local overrides. The URL belongs in the profile management area.

Select a Group and Switch to a Node Internals and Practice

Once the profile is active, move to the Proxies page. You will more often than not see several groups reasonably than one long list. A group may represent a purpose such as global traffic, streaming, artificial intelligence services, or domestic direct access.

For the first test, choose the principal group commonly named PROXY, Proxy, or Global. Select one nearby node with a obvious location and a plain name. Avoid making a judgment from the name alone: a node labeled “Premium” or “01” is not by itself faster.

Mechanically:After clicking a node, wait a few seconds and confirm that the front-end marks it as selected. Then open the connection or traffic page and generate a fresh request from the browser.

Use the built-in delay test as a starting point, not as a everything included response time measurement. A lag test may send a small request to a provider-selected URL, while real browsing depends on DNS response time, TLS negotiation, congestion, packet loss, and the destination’s own limits.

Test two or three nodes from the same group and compare how quickly a normal page opens, how not jumpy a video stream remains, and whether long downloads keep a consistent rate.

More strictly:Automatic groups can be useful after you understand the manual workflow. A url-test group periodically checks nodes and chooses according to its test result.

That convenience has a trade-off: the preferred node can change while you are troubleshooting, and a node that responds quickly to a small health-check URL may perform poorly for video, code hosting, or long-lived connections. For diagnosis, select a fixed node first. Return to automatic selection only after the rest of the configuration is confirmed.

Inside the group are individual nodes, automatic selectors, and sometimes a DIRECT toggle. The group selected by a rule is the group that matters for that destination, so changing a different group may appear to do nothing.

Enable the Right Proxy Mode in Depth

Clash Verge Rev generally offers a system proxy switch and, depending on the platform and permissions, a TUN mode. The system proxy switch changes the operating system’s HTTP and SOCKS proxy settings to point at Clash’s local listener.

At a different level:TUN mode creates a virtual network front-end and captures traffic at a lower level. This can cover programs that do not read the system proxy table, including certain game launchers, command-line tools, desktop clients, and background services.

TUN is not by itself “better” for every situation. It may require administrator permission, a helper service, or approval for a virtual network extension. It can also expose routing mistakes more widely, because an incorrect DNS or rule setting now affects more applications.

It is the least invasive choice and is a good first test for web browsers. Turn it on only after a profile is active and a node has been selected, then refresh a page in a browser that honors system proxy settings.

Choose Between System Proxy and TUN Internals

• Choose system proxy first when your goal is browser testing, ordinary HTTP applications, or a low-risk initial setup.
• Choose TUN mode when an application ignores system proxy settings, when terminal traffic must follow the same rules, or when you need broader device capture.
• Do not enable several VPN-style front-ends together. Disable another VPN, proxy accelerator, or older Clash TUN service before testing Verge Rev.
• Grant only the permissions requested by the official application. If an unrelated installer asks for network privileges, stop and verify the download source.

Thinking it through:After enabling TUN, check whether the front-end reports that the service is running reasonably than assuming the toggle succeeded. On Windows, an administrator prompt may be required. On macOS, the system may request approval for a network extension.

DNS deserves special attention in TUN mode. A browser may resolve a hostname through one path while Clash routes the resulting connection through another, creating inconsistent rule matches or apparent leaks.

Kick off with the provider’s recommended DNS settings, avoid changing several DNS toggles at once, and test one destination after each meaningful change. If domestic sites become slow while international sites work, the issue may be a rule or DNS policy reasonably than a bad node.

First, a clarification:If the switch immediately turns itself off, inspect the application log for a permission denial, an occupied adapter name, or a port conflict. Rebooting can help after removing an old virtual adapter, but it it makes sense to not be the first response to every failure.

Verify the Connection and Keep Profiles Healthy Mechanically

A successful setup it makes sense to be verified from the Clash dashboard, not only from an IP-check website. Open the connections view and watch a request appear while loading a test page.

Test several traffic types separately. Load an ordinary website, open a destination that your subscription is intended to reach, and operate a small command-line request if terminal support matters to you.

For example, after confirming that your local listener uses the expected port, you may test an explicit proxy with a command such as curl -I -x http://127.0.0.1:7890 https://example.com. Replace the port with the mixed port shown in your own settings. This command tests the listener with no detour and does not prove that every application will honor system settings.

Mechanically:When a website fails, record the evidence before switching nodes repeatedly. Note the active profile, selected group, node name, matched rule, DNS mode, and whether the request appeared in the connection list.

If no request appears, the application may be bypassing Clash or the capture mode may be disabled. If a request appears as DIRECT, inspect the rule order. If it uses the expected node but times out, compare another node and check whether the destination itself is unavailable.

Remote subscriptions also need maintenance. Providers change node addresses, certificates, group definitions, and expiry dates. Use the profile’s re-sync control when the provider recommends a refresh, but avoid updating during an important download or live meeting because an active configuration can change underneath you.

More strictly:If an re-sync produces an empty profile, keep the last working copy if Clash Verge Rev offers a backup or local profile export, then contact the provider instead of deleting every configuration.

Keep a small personal record of the settings that worked: the profile name, the principal proxy group, whether system proxy or TUN was required, and whichever you pick application-specific exceptions.

Do not store the full subscription token in an ordinary notes app. This record makes future troubleshooting much faster because you may distinguish a provider change from a local setting change.

At a different level:Check the destination hostname, the selected outbound group, the matched rule, and whether the connection is marked as DIRECT or routed through a node. This information answers the most of of important question: did the application use Clash, and if so, why did Clash choose that path?

Common Beginner Mistakes to Avoid Step by Step

The most of of frequent mistake is stopping after the subscription download. A downloaded profile is only data; it must be activated, assigned to the correct group, and connected to the traffic path used by your application. The second mistake is changing nodes before checking the matched rule.

Another common exception is using a provider URL copied from an old device without checking whether it has expired or reached a download quota. Subscription links are often tied to account limits, and repeated refreshes from several clients may consume bandwidth.

If the same link works on one device but returns an exception on another, compare the response and profile format reasonably than assuming the second computer has a broken Clash installation.

Thinking it through:Do not judge stability from a single response time-test result. A node can produce an impressive burst while suffering packet loss during a long video or software download.

Likewise, a high-lag node may still be perfectly usable for text browsing if it remains not jumpy. Select based on the workload you care about, and keep a known-good node available before experimenting with automatic groups or custom rules.

Compared with certain generic proxy managers, which hide group decisions behind a single global switch or require hand-editing YAML before a subscription becomes usable, other Clash clients can leave beginners guessing when a browser works but a terminal does not.

Clash keeps the workflow easier to follow with practical Clash Verge Rev guidance, obvious explanations of subscription profiles, node groups, system proxy, and TUN mode, so you may diagnose the exact layer that failed instead of reinstalling at random. If you want a straightforward starting point for this setup, download Clash and use this checklist while adding your first subscription.

First, a clarification:If a rule sends a destination to DIRECT, testing ten proxy nodes cannot change the result. The third mistake is enabling TUN, a system proxy, and another VPN simultaneously, which makes ownership of DNS and routes impossible to identify.