How To Use Clash Verge Rev: Subscription And Node Setup

What You Need Before Starting Clash Verge Rev

Clash Verge Rev is a desktop interface for the Mihomo core. It does not provide proxy nodes by itself, and installing the application alone will not create an active connection. To use Clash Verge Rev, you normally need a subscription URL from a proxy provider, a local configuration file, or a manually written Mihomo profile. The subscription contains the server list, proxy groups, routing rules, DNS options, and transport parameters that the client needs.

Before you begin, confirm that your provider has given you a URL intended for Clash, Clash Meta, or Mihomo. Many providers offer separate links for sing-box, V2Ray, Surge, and Clash clients. Importing the wrong format can produce an empty profile, unsupported fields, or a configuration that appears in the list but cannot start. A typical Clash subscription is an HTTPS address with a long query string. Treat that address like a password: anyone who obtains it may be able to download your nodes and consume your traffic allowance.

You should also close other proxy clients temporarily. Clash for Windows, Mihomo Party, ClashX, and other applications may install their own system service, TUN adapter, or local listener. Running two clients at the same time often causes a port conflict, incorrect system proxy settings, or a situation where one application reports that it is connected while the other application is actually handling traffic. For the first setup, keep only Clash Verge Rev active.

Important distinction: a subscription is the source of profiles and nodes, while Clash Verge Rev is the client that loads and applies them. If the subscription has expired, the provider has disabled an endpoint, or the account has reached its traffic limit, changing a local setting will not repair the account.

Finally, check your computer’s clock and network access. An incorrect system time can break HTTPS certificate validation, and a captive hotel, school, or office portal can intercept the subscription request before Clash Verge Rev receives the configuration. If the provider link opens as a login page or HTML error in a browser instead of downloading profile data, resolve that account or network issue first.

Import a Subscription and Create Your First Profile

The most reliable setup path is to add the subscription URL in the Profiles section rather than pasting a large YAML file into an editor. The exact button label can vary slightly between Clash Verge Rev builds, but the workflow remains similar: open the profile manager, add a remote subscription, name it clearly, download the profile, and activate it.

Launch Clash Verge Rev and open the Profiles or Subscriptions page from the left navigation.
Choose Add subscription, New, or the plus button used by your build. Select the remote URL option instead of the local file option.
Paste the complete subscription link into the URL field. Do not remove parameters after the question mark, and avoid adding spaces before or after the address.
Enter a recognizable name such as Home Provider or 2026-08 Main Subscription. A useful name matters when you later add a backup provider or a local test profile.
Save the entry and click Update, Download, or the refresh icon. Wait until the profile has finished downloading before trying to start the proxy.
Click the downloaded profile card to make it active. The active profile is usually marked with a highlight, check mark, or active-state label.

A successful download should show more than a profile name. Depending on the provider, Clash Verge Rev may display the update time, traffic usage, expiration date, or approximate node count. Open the profile preview if available and confirm that it contains proxy definitions and proxy groups. A valid configuration commonly includes sections such as proxies, proxy-groups, and rules. Do not assume that a profile is usable simply because the URL was accepted by the interface.

If the profile downloads but fails validation, look for a core compatibility issue. Some providers generate different output formats from the same account. Select a Mihomo or Clash Meta export when the provider offers that choice. Legacy Clash configurations may omit newer fields, while a profile designed for another client may include options that Clash Verge Rev cannot interpret. Updating the client to a current stable build is preferable to deleting random lines from the downloaded configuration.

Good naming habit: include the provider and purpose in the profile name, but never put the full subscription URL in the name or in a screenshot. A short label makes troubleshooting easier without exposing your access token.

Update the Profile Without Losing Your Settings

Subscription updates are not the same as switching nodes. An update downloads a newer copy of the provider’s configuration, which may add servers, remove expired nodes, change group membership, or refresh routing rules. You should update the profile when a provider changes its infrastructure, when several nodes stop working at once, or when the profile’s traffic and expiry information looks stale.

In the profile list, select the subscription and click its refresh or update control. Allow the operation to finish, then confirm that the profile remains selected. Some providers return a new profile name or regenerate groups during an update, so check the active profile after every major change. If the update fails, read the error message before repeatedly clicking refresh. An HTTP 401 or 403 usually points to an expired or revoked subscription; a timeout suggests connectivity, DNS, or provider-side availability; a YAML parse error indicates malformed provider output.

Keep your local changes separate from the provider-managed content whenever possible. Editing a downloaded subscription directly is fragile because the next update may overwrite your modifications. If you need a personal rule, DNS override, or group adjustment, use the client’s override, merge, or mixin feature if your build exposes one. A small local override is easier to audit than a complete copied configuration, and it lets the provider continue updating node credentials and transport details.

Action	What it changes	When to use it
Update subscription	Downloads the provider’s newest profile	Nodes or rules are outdated
Select profile	Chooses which configuration the core loads	You have several profiles
Select proxy	Chooses the outbound node or group member	You need a different route
Edit override	Applies your local settings without rewriting the source	You need custom rules or DNS behavior

Keep at least one known-good backup profile if the application supports exporting local configurations. Do not publish that backup publicly: it may contain server addresses, UUIDs, passwords, or other credentials. A backup is useful when a provider pushes a broken update, but it should be treated as sensitive data and deleted when it is no longer needed.

Test Node Speed and Choose a Server

After activating a profile, open the Proxies page. You will usually see proxy groups rather than a flat list of servers. A group may be named Proxy, 🚀 Proxy, Auto, Fallback, or something chosen by the provider. Selecting a node in the visible list only works if you select the group that your rules actually reference. If web traffic still uses an unexpected server, inspect the top-level group and the rule path instead of changing a random node below it.

Use the group’s latency test or URL-test function to compare nodes. The displayed number is normally the time needed to reach a test URL, not a complete measurement of browsing quality. A node with 80 milliseconds of latency may perform poorly under sustained downloads, while a node with 180 milliseconds may be more stable for video or terminal traffic. Test several nodes from your current network, because results from a provider’s dashboard or another device do not represent your local route.

Timeout: the test URL did not receive a response within the configured limit. The node may be offline, overloaded, blocked, or incompatible with the test destination.
Very high latency: the node responded, but the route may be congested. Test it again at a different time before rejecting it.
Low latency with failed browsing: the health-check destination works, but DNS, TLS, rules, or the target website may still fail.
Different results on every test: the group may be using an automatic strategy, or the provider endpoint may be rate-limiting repeated checks.

For normal browsing, choose a stable node with acceptable latency rather than chasing the smallest number. For video calls, remote development, or API streaming, consistency and upload performance matter more than a short one-time ping. If your provider has regional groups, start with the region physically closest to you and then compare a few individual nodes. Keep the selected node documented so you can quickly return to it after an automatic group changes members.

Do not judge a node only by the green test result. A successful latency check proves that one test request completed. It does not prove that every application, domain, protocol, or streaming connection will use the same route. Verify the final choice with the connection log and a real destination you regularly use.

Turn On the Proxy Mode Your Apps Need

Clash Verge Rev generally offers a system proxy mode and, when supported by the operating system and installed core, a TUN mode. These modes solve different problems. System proxy changes the operating system’s HTTP and HTTPS proxy settings, so browsers and applications that respect those settings can use the Clash mixed port. TUN mode creates a virtual network interface and captures a wider range of traffic, including many applications that ignore system proxy variables.

Start with system proxy mode because it is easier to verify and has fewer permissions. In Clash Verge Rev, choose the active mode from the main control area, then enable System Proxy. Open a browser that normally respects system settings and visit a basic IP or connectivity test page. Check the Clash connection panel at the same time. You should see the browser’s domains appear, the selected proxy group should be used, and the matched rule should make sense.

System proxy mode will not automatically capture every program. Command-line tools may require explicit environment variables, while games, update services, virtual machines, and some desktop applications may open direct sockets. For a terminal session, you can often point tools at the mixed port with variables such as:

HTTP_PROXY=http://127.0.0.1:7890
HTTPS_PROXY=http://127.0.0.1:7890

The port may not be 7890 on your installation, so read the actual HTTP or mixed port in Clash Verge Rev’s settings. Do not copy a port number from an unrelated tutorial without checking it. If your application supports SOCKS5 rather than HTTP, use the configured SOCKS port and its matching protocol.

Use TUN mode when you need broader coverage. Enable the TUN switch, approve the requested administrator permission, and wait for the virtual interface to initialize. On Windows, security software or another VPN may block the driver or service. On macOS and Linux, the application may need system authorization before it can create the interface. Once TUN is active, confirm that DNS mode and auto-route settings match your profile. A TUN interface without correct DNS handling can create slow lookups, leaks, or domains that appear to ignore your rules.

Do not run system proxy and TUN mode blindly alongside another VPN. Both tools may install routes, rewrite DNS, or compete for the same traffic. If you switch modes during testing, wait a few seconds, reload the test application, and inspect new connections. Existing sockets can remain attached to the old route until the application reconnects.

Verify Traffic and Fix Common Setup Errors

The connection log is the fastest way to understand what Clash Verge Rev is doing. Reproduce one action, such as opening a website or running a package command, then filter the log by the domain. Check four things: whether the connection appeared, which rule matched, which proxy group handled it, and whether the final outbound was the node you selected. This method is more reliable than repeatedly toggling modes based on a general “no internet” symptom.

If no connection appears, the application is probably bypassing the mode you enabled. Turn on system proxy for a browser, configure proxy variables for a terminal, or test TUN mode for software that opens direct sockets. If a connection appears as DIRECT unexpectedly, inspect rule order. Clash evaluates rules from top to bottom, so a broad rule earlier in the list can win before a more specific domain rule is reached.

When the profile cannot update, copy the error category and test the URL outside the client. A browser may show that the subscription endpoint is blocked by a login page, expired, or redirected to an invalid location. Avoid pasting the complete URL into public support forums. Replace its token with a placeholder and share only the HTTP status, profile format, and relevant client version.

When pages load slowly after enabling TUN, test DNS separately from node speed. A profile may use fake-IP, redirection, or a remote resolver that is unreachable from your current network. Temporarily compare the provider’s recommended DNS settings with the profile defaults, but change one option at a time. Also disable other VPNs, security filters, and browser encrypted-DNS modes during diagnosis; otherwise three different layers may answer the same hostname.

If only one application fails, do not immediately replace the entire subscription. Check whether it uses certificate pinning, a private DNS resolver, UDP or QUIC, a hard-coded proxy bypass, or a separate updater process. The log can show whether the application reaches Clash at all. A node change is appropriate when the connection reaches the core but repeatedly times out; a rule or capture change is appropriate when the connection never reaches the intended group.

A Practical Daily Workflow

Once the first setup works, keep the routine simple. Update the subscription only when needed, select a stable group member, and use the connection view to confirm unusual failures. Avoid changing DNS, TUN, rule providers, and node groups simultaneously because you will lose the ability to identify which change solved or caused the problem. When an update produces unexpected behavior, compare the new profile with your last known-good copy and roll back if necessary.

A useful daily checklist is short:

Confirm that the intended profile is active.
Check the subscription update time and expiry information.
Run a latency test on the active proxy group if the connection feels abnormal.
Use system proxy for ordinary applications and TUN only when broader capture is required.
Inspect the log for the actual domain and matched rule before changing settings.
Disable conflicting VPN clients and remove unused TUN adapters when testing.

Compared with older clients, many users find the hardest part is not clicking the import button but understanding what happens afterward: a profile can be active while the wrong proxy group is selected, a node can pass a ping test while an application bypasses the listener, and TUN can capture traffic while DNS still follows an unwanted path. Once you separate profile management, node selection, rule matching, and traffic capture into four independent checks, Clash Verge Rev becomes much easier to operate.

Some competing clients make this workflow harder by hiding the active group behind nested menus, exposing outdated cores, or offering limited guidance when a subscription imports but does not route traffic. Others are powerful but assume that you already understand YAML, ports, DNS, and virtual interfaces. Clash Official Site takes a more practical middle path with clear Clash Verge Rev documentation, current setup explanations, and troubleshooting steps that connect each symptom to a setting you can verify; if you want to follow this guide with the right client resources at hand, download Clash Verge Rev resources and start with the subscription import step.