Clash Verge Rev How To Use: Add Subscriptions & Switch Nodes

Understand the Clash Verge Rev workflow

After installing Clash Verge Rev, the application window may look ready before any traffic can actually be proxied. A working setup requires several separate steps: import a profile, download its subscription data, start the mihomo core, choose a proxy policy, and enable either the system proxy or TUN mode. These steps are related, but they are not interchangeable. Importing a subscription does not automatically activate a node, and selecting a node does not necessarily route traffic through it.

Clash Verge Rev is a graphical client. It manages profiles, starts the proxy core, displays logs, changes policy-group selections, and applies system networking settings. The mihomo core performs the actual work: parsing YAML, resolving domains, matching rules, opening outbound connections, and listening on local ports. A subscription provider supplies configuration content, which commonly includes proxies, proxy groups, rules, DNS settings, and update metadata.

Item	What it does	What you should check
Profile	Stores the imported YAML or subscription source	It appears in the Profiles list and has a recent update time
Subscription	Provides nodes, groups, and rules from a remote URL	The URL is complete and returns valid Clash-compatible content
mihomo core	Processes traffic and exposes local proxy ports	The core is running without YAML or port errors
Proxy group	Chooses one node or another group for matched traffic	The intended node is selected in the active group
Traffic mode	Determines whether requests follow rules, use one global proxy, or go direct	`Rule` is normally the practical default
System proxy or TUN	Connects applications to the local proxy engine	The switch is enabled only after the core is ready

Before configuring anything, close other proxy clients that may still be active. Two applications listening on the same address, often 127.0.0.1:7890, can produce port conflicts and confusing results. If another client has enabled the system proxy, turn it off temporarily so that Clash Verge Rev can take control cleanly.

Import and update a subscription

Open Clash Verge Rev and go to the profiles or configuration page. Depending on the build and language, the relevant control may be labeled Profiles, Config, Import, or New Profile. Choose the option for importing from a URL rather than importing a local file. Paste the complete subscription address, give the profile a recognizable name, and confirm the import.

Copy the complete subscription URL from the provider’s dashboard.
Open the profiles page in Clash Verge Rev.
Choose URL import or add a remote profile.
Paste the URL without adding spaces or line breaks.
Save the profile and wait for the first download to finish.
Click the imported profile to make it active.
Start the core and inspect the logs for parsing errors.

A profile that appears in the list is not necessarily the active profile. Look for a highlight, check mark, radio button, or active-state indicator. If several subscriptions are present, select the one that contains the latest node list and the policy groups you expect. The active profile determines which nodes and rules appear on the proxy page.

Verify the first download

After importing, use the profile’s refresh or update button. A successful response should produce readable configuration data or a parsed list of proxies and groups. If the interface reports a status code, 401 commonly means that the token is invalid or expired, while 403 may indicate a provider policy or request-header problem. A 404 usually means that the old address no longer exists, and a timeout points to DNS, routing, or server availability.

Do not assume that a browser opening the URL proves that the subscription is usable. The response could be an HTML login page, an account-expired notice, or a JSON error. Clash-compatible content should contain configuration fields such as proxies, proxy-groups, rules, or other valid YAML structures. If the downloaded content begins with <!doctype html>, it is a web page rather than a proxy configuration.

Once the profile works, configure an update interval that matches the provider’s policy. A daily interval such as 1440 minutes is usually less aggressive than repeatedly pressing update. Very short intervals can trigger 429 Too Many Requests, consume subscription traffic, or cause the provider to temporarily block the address. If the provider publishes a recommended interval, follow that value instead of guessing.

profile: Daily subscription
update interval: 1440 minutes
active mode: Rule
mixed port: 7890
controller port: 9090
TUN: disabled until system proxy is verified

When a profile is generated for a particular client or core, compatibility matters. mihomo supports many modern fields and protocols, but a provider may still return a configuration containing unsupported values, invalid YAML indentation, or a proxy type that the current build cannot load. Check the core log immediately after an update. A profile with some visible node names can still contain parsing problems that affect rules, DNS, or policy groups later.

Test and select a proxy node

With the profile active, open the proxies page. You will usually see policy groups such as Proxy, 节点选择, Auto, Streaming, or names chosen by the subscription provider. The top-level group is often the one referenced by the rules. Selecting a node inside a lower-level group may therefore change actual traffic, while selecting an unrelated group may have no visible effect.

Start by identifying the group used for ordinary proxy traffic. In a typical configuration, a rule may end with a policy name such as Proxy, and that group may contain individual nodes plus options such as DIRECT or another nested group. Select the group, then choose a node from its list. The selected item should remain highlighted after you switch pages or restart the core.

Run latency tests before judging a node

Use the group’s delay, latency, or test button to compare nodes. The test normally sends an HTTP request to a fixed URL and measures response time; it does not prove that every website, streaming service, or application will work. A node showing 80 ms may still fail on a destination blocked by the provider, while a node showing 220 ms may offer more stable throughput.

Observation	Likely meaning	Next action
Low delay and pages load normally	The node is currently responding well for the test destination	Use it for general browsing and monitor stability
Timeout	The node, route, or test endpoint did not respond in time	Test another node and check the core log
Very low delay but downloads are slow	Latency does not measure sustained bandwidth	Compare a larger download or several real destinations
Node works for one service but not another	Destination policy, regional access, or protocol behavior differs	Use a dedicated streaming or regional group if provided
All nodes fail	The problem may be the profile, DNS, local port, or provider service	Check core status before changing individual nodes

For a first test, choose one stable-looking node manually rather than immediately relying on automatic selection. Open the client’s connection or log view and generate a request from a browser. The log should show the destination, matched rule, selected policy, and outbound connection result. If the request is marked DIRECT when you expected a proxy, the issue is probably the mode or rule selection rather than the node itself.

Change proxy modes and enable traffic routing

Clash Verge Rev commonly exposes three traffic modes: Rule, Global, and Direct. In Rule mode, the configuration evaluates rules from top to bottom and sends each request to a policy such as a proxy group, DIRECT, or REJECT. This is the normal everyday mode because domestic, local, and proxy-required destinations can be handled differently.

Mode	Behavior	Suitable use
Rule	Routes traffic according to the YAML rule list	Daily browsing, mixed local and external traffic
Global	Sends matching application traffic through one selected proxy policy	Testing a node or temporarily forcing proxy routing
Direct	Bypasses proxy routing and connects directly	Diagnosing whether the proxy causes a problem

Use Global as a diagnostic tool rather than a permanent replacement for well-maintained rules. It can quickly show whether a selected node can reach a destination, but it may send local services, private addresses, and sites that should remain direct through the proxy. Return to Rule after testing. If a website fails in Rule mode but works in Global mode, inspect the matched rule and the policy group assigned to it.

Enable the system proxy first

After the core is running and a node has been selected, enable the system proxy switch in Clash Verge Rev. On Windows and macOS, this usually modifies the operating system’s HTTP and HTTPS proxy settings to point to a local address, often 127.0.0.1:7890. The exact port comes from the active configuration and may be different, so do not hard-code it when troubleshooting.

Confirm that the mihomo core status shows running.
Confirm that the active mode is Rule or the mode you intend to test.
Select a node in the main proxy group.
Enable the system proxy switch.
Open a browser and visit a few unrelated destinations.
Check the connections or logs to confirm the selected policy.

System proxy mode covers browsers and applications that respect the operating system proxy settings. It does not automatically capture every program. Command-line tools, games, virtual machines, containers, and applications with their own network stack may bypass the system proxy. If those applications must also be routed, consider TUN mode, but configure it only after ordinary system proxy mode works.

Configure TUN and launch at startup carefully

TUN mode creates a virtual network interface and allows the core to handle traffic from applications that do not read the system proxy. It may require administrator permission, a network extension approval, or a system service depending on the operating system. TUN also changes DNS and routing behavior, so it introduces more variables than a simple system proxy.

Before enabling TUN, turn off other VPN applications and confirm that the profile contains suitable DNS settings. Enable TUN from the settings page, accept the requested permission, and restart the core if the client asks you to. Test one application at a time. If the system loses connectivity, disable TUN and return to system proxy mode, then inspect the core log for DNS, route, or permission errors.

Setting	Recommended starting point	Reason
Traffic mode	`Rule`	Allows direct and proxied destinations to coexist
System proxy	Enable after the core is confirmed running	Easy to test and easy to disable
TUN	Leave disabled initially	Avoids unnecessary routing and permission complexity
Launch at startup	Enable only after the profile is stable	Prevents an invalid profile from taking over the network at login
Auto-update	Use the provider’s interval, commonly once per day	Reduces rate limits and unexpected configuration changes

To enable launch at startup, open the general settings page and find an option such as Launch at startup, Start on boot, or Start with system. If there is a separate option for automatically enabling the system proxy or TUN, treat it cautiously. Start the application automatically first, but leave automatic traffic capture disabled until you have confirmed that the profile updates correctly and the selected core starts without errors.

A reliable startup sequence is: launch Clash Verge Rev, load the last active profile, start mihomo, restore the selected policy group, and then apply the system proxy. If startup leaves the system offline, disable automatic proxy activation from the client’s settings or the operating system proxy panel, open Clash Verge Rev manually, and inspect the logs. Common causes include an expired subscription, a changed node format, a port already occupied by another application, or a TUN permission that was revoked after an operating-system update.

Once the subscription refreshes normally, the selected group works, and system proxy mode passes ordinary browsing tests, Clash Verge Rev is ready for daily use. Keep the original subscription address backed up privately, avoid unnecessary manual refreshes, and revisit the active node when a provider changes its server list. For platform packages and installation guidance, see the download center.