Tutorial November 15, 2026

Clash Verge Rev Setup Guide: Add a Subscription and Pick Nodes

Learn how to add and refresh a proxy subscription in Clash Verge Rev, select a node, and confirm that the connection works. Clear, beginner-focused steps help you move from a newly installed app to everyday use.

Docker Proxy GitHub Acceleration Advanced Config YAML

1. Before you add a subscription: know what you are importing

Clash Verge Rev is a desktop client built around Mihomo. It can load a remote subscription, keep that configuration refreshed, and let you choose which available proxy node handles your traffic. If you have just installed the app, it helps to separate those jobs: adding a subscription gives the client a profile to use; selecting a node decides which route a proxy group will use; and testing the connection checks whether the chosen route works from your device. A successful import alone does not prove that a node is reachable, and a connected node does not guarantee that every application is using the system proxy.

Before opening the app, get the subscription URL from the service that provides your proxy access. It is usually a long HTTPS address, sometimes accompanied by an expiry date, traffic allowance, or device limit. Copy the full address using the provider’s own dashboard or instructions. Do not substitute a website login URL, a single-node connection link, or a random YAML file unless the provider explicitly says it is compatible with Mihomo. Subscription links can contain account credentials, so treat them like passwords: do not post them in screenshots, public support requests, shared documents, or browser history on a device other people use.

Check a few basic details before importing. Confirm that your plan is active, that the provider permits use with Clash Verge Rev or Mihomo, and that your operating system can reach the provider’s subscription endpoint. If the provider supplies a dedicated Clash or Mihomo subscription address, prefer that over a generic one. Some services offer multiple formats, and a format intended for another client may omit rule providers, proxy groups, or metadata that the profile needs. If the dashboard has a button labeled for copying a subscription URL, use it rather than manually selecting a URL from surrounding text.

You may also see a configuration file download instead of a subscription URL. A local YAML profile is imported from a file and generally does not refresh itself from the provider. A remote subscription, by contrast, can usually be updated from within Clash Verge Rev when nodes or settings change. The two approaches can both work, but they have different maintenance expectations. If you are unsure which one you received, ask the provider whether it is a remote subscription link or a one-time configuration file before changing settings.

Finally, avoid changing several network settings at once. Keep a note of the current system proxy and service-mode state, and make a small change only when a test indicates it is needed. This makes it easier to tell whether a failure comes from the subscription, a selected node, DNS, or an application that is not using the proxy. Menu labels can shift between Clash Verge Rev releases, so follow the names shown in your installed version rather than relying on instructions for an older build.

2. Add the remote profile in Clash Verge Rev

Open Clash Verge Rev and locate the profile-management area. Depending on the release, it may be labeled Profiles, Profiles and Configs, or simply appear as a page where available configurations are listed. Look for the control to add a remote profile or import a subscription. Paste the complete subscription URL into the URL field, give the profile a recognizable name, and confirm the import. A useful name describes the provider or purpose without exposing account details, such as “Personal profile” or “Work-approved relay.”

After you submit the address, the client needs to contact the provider and retrieve the profile. On a successful import, the new entry should appear in the profile list. Select or activate it if the interface has not done so automatically. Do not assume that seeing a profile in the list means it is the active configuration: check for a selected state, active indicator, or equivalent status in your version. If another profile remains selected, the app may continue using that configuration even though the new one imported correctly.

If the client reports an error, read the message before retrying. A timeout points toward a reachability problem; an authorization or HTTP status error may mean the URL is expired, copied incorrectly, or restricted by the provider. A parse error can indicate that the response is not a valid Clash/Mihomo configuration, or that a provider is returning an HTML sign-in page instead of a profile. Repeatedly pasting the same URL will not fix an expired credential. Check the provider dashboard, copy a fresh link if necessary, and confirm that the operating system’s date and time are correct if certificate validation fails.

Once the profile is active, inspect its displayed name and any provider-supplied update information. Some providers include a traffic or expiry notice in profile metadata; others do not. Treat that display as helpful information, not as an independent billing record. The provider’s account page remains the authority for plan status and usage. It is also worth keeping the original subscription URL somewhere private and secure, because you may need it again after reinstalling the client or setting up another authorized device.

A profile may contain many nodes and several groups rather than one directly selectable server. That is normal. Groups can represent automatic selection, fallback behavior, regional choices, or a general proxy policy. The group names are defined by the configuration and vary between providers, so a label such as “Select,” “Proxy,” or a region name is not guaranteed to mean exactly the same thing in every profile. Start by finding the group intended for general proxy use; avoid editing YAML just to make the list look simpler.

3. Refresh the profile and understand what the list means

A remote profile is not necessarily a live view of the provider’s latest settings. The client stores a copy locally, so a provider may add, remove, or rename nodes without the changes appearing until you update the profile. In the profile list, use the refresh or update control associated with the subscription. Wait for the request to finish and check whether the app reports a successful update. If the profile has an automatic-update option, its interval may be configured by the provider or the client; do not assume a refresh happens instantly whenever the provider changes something.

Refreshing replaces or updates profile data, but it may not preserve every local edit. If you have customized rules or settings in a provider-managed profile, read the client’s behavior and the provider’s instructions before refreshing. A remote subscription is commonly treated as provider-owned configuration, so locally editing its generated contents can make changes difficult to maintain. When you need a durable custom setup, use a supported merge, override, or separate configuration workflow rather than editing the subscription URL’s downloaded content without a backup.

The proxy page is where you usually select a node or group after the profile is active. A group is a policy choice that can contain other groups or individual nodes. An automatic group may test candidates and choose one according to its configured rules; a manual selection group lets you choose an entry yourself. A node is the actual endpoint shown beneath a group, often with a region, protocol, or provider-assigned label. Selecting a group is not always the same as selecting a particular node: inspect the nested choices and make sure the selection you intend is active.

Names alone are not a reliable measure of quality. A label that mentions a nearby city does not prove that the endpoint is physically there, and a premium-sounding name does not promise low latency. Use the client’s available delay or connectivity test as an initial comparison, then validate the route with an actual page or application. A delay test is a short measurement to a particular test destination; it does not predict every site’s performance, streaming behavior, or ability to maintain a long session.

What you see What it usually represents What to check
Profile entry A remote or local configuration available to the client Whether it is the active profile and when it last updated
Proxy group A policy that chooses or organizes one or more routes Whether it is automatic, manual, or nested inside another group
Node An individual proxy endpoint supplied by the profile Whether its test succeeds and the intended group has selected it
System proxy or TUN A way to send supported device traffic through Mihomo Whether the mode is enabled and appropriate for your use case

Do not change the profile’s rules simply because the first visible group is unfamiliar. Many profiles route some traffic directly and other traffic through a proxy group. That means a successful node selection may affect only traffic that the active rules assign to that group. Understanding this distinction prevents a common false diagnosis: a browser that still reaches a local site directly does not necessarily mean the node failed, and an application that ignores the system proxy may not be covered unless an appropriate TUN setup is configured.

4. Choose a node and verify the route

Use the following sequence as a first-run check. Exact button names can vary by release, but the order is stable: activate the profile, choose the relevant group, select or test a node, enable an appropriate traffic mode, and verify the result in more than one place. If you are on a managed work or school network, follow its proxy and device policies before enabling traffic capture.

  1. Activate the imported profile. Return to the profile page and confirm that the subscription you added is selected. If the app displays a profile status or update timestamp, make sure it does not show an import error.
  2. Open the proxy groups. Find the group intended for ordinary proxy traffic. If the group contains nested groups, open the relevant one until you can see the individual node choices. Do not select a special-purpose group, such as one intended only for a specific service, unless that is the traffic you mean to test.
  3. Test a few candidates. Use the delay-test control if available, and compare several nodes from the same group. A test that times out means the test destination was not reached through that candidate at that moment; it does not prove that every other route is broken. If the provider recommends a particular test URL, use that rather than assuming a generic target is suitable.
  4. Select a node or automatic policy. For a predictable first test, choose a node with a successful result and a reasonable delay. Alternatively, choose an automatic group if you want the profile to make that decision. Wait for the selection indicator to update before moving on; a click that did not change the active row may not have changed the route.
  5. Enable the traffic mode you need. System proxy is often sufficient for browsers and desktop apps that honor the operating system proxy. TUN mode can capture a broader range of application traffic, but it may require elevated permission, service mode, or a driver component depending on the operating system. Use only the mode you understand, and avoid enabling multiple overlapping proxy tools while testing.
  6. Check a real connection. Open a site that should use the selected route, then look at the client’s connection or traffic view if available. A request appearing there is evidence that the client handled it; an external IP-check page can provide a separate indication of the public exit address. Test more than one destination if your rules intentionally treat different domains differently.

The practical result should agree across the selection indicator, the connection view, and the application you are testing. If the selected node is healthy but no connections appear in the client, the application may be bypassing the system proxy, the system proxy may be off, or the active rules may send that destination directly. If connections appear but the destination fails, check the node and the target service separately. This is more useful than repeatedly switching nodes without observing what changed.

For routine use, choose a route based on the workload rather than just the smallest delay number. A nearby node may be suitable for browsing, while a different route may be more stable for a long download or video call. Automatic groups reduce manual maintenance, but their choice depends on the provider’s configuration and the test behavior. Manual selection gives you control, but you need to notice when a node becomes unavailable. Either approach is reasonable; record which group you selected so you can reproduce a known-good setup later.

5. Troubleshoot common failures and keep the setup reliable

When a subscription will not import, first determine whether the client reached the subscription service. Check the URL for missing characters, whitespace, or a line break introduced during copying. If it is correct, confirm that the provider has not expired or rotated the link and that the service permits requests from your network. A browser opening the same URL may display raw configuration, an error page, or a login prompt; any of those outcomes can offer clues, but avoid sharing the complete URL while asking for help because it may grant access to your account.

When nodes appear but tests fail, separate endpoint reachability from profile validity. Update the profile once, test more than one node, and inspect whether the provider reports maintenance or regional restrictions. If every node fails at the same time, verify basic internet access and system time before assuming every endpoint is down. A local firewall, another VPN, security software, or a captive Wi-Fi login can interfere with traffic. Temporarily disabling a conflicting proxy may help isolate the cause, but do not weaken security controls on a managed device without permission.

When a node test succeeds but a website does not load, inspect the selected group and the active traffic mode. The group may be nested, the application may use its own proxy settings, or a rule may route that domain directly. Check the client’s connection log while reproducing the issue, and look for the destination, chosen policy, and final route. If the request never appears, investigate how the application sends traffic. If it appears and uses the expected node, try another test destination and check for a service-side error before changing DNS or editing rules.

If only some applications work, remember that system proxy support is not universal. Browsers commonly use the operating system setting, but command-line tools, games, launchers, and applications with embedded networking stacks may behave differently. TUN can cover more traffic, but it is not a magic repair for every application: routing rules, DNS behavior, permissions, and IPv6 handling still matter. Change one relevant setting at a time, restart an application when it may have cached proxy settings, and verify the change using the client’s traffic view.

A dependable routine is simple: check that the profile is active, refresh it when the provider recommends or when its node list looks stale, test the group when performance changes, and confirm the route after changing system proxy or TUN settings. Keep private subscription links out of logs and screenshots. If you need provider support, share the client version, operating system, the visible error text, and a redacted description of the selected group—not the full credential-bearing URL or an unredacted configuration file.

Some one-click VPN tools make the first connection feel simpler, but they may offer fewer visible choices when you need to refresh a provider profile, compare individual nodes, or understand why a particular application took a direct route. Clash Verge Rev exposes those steps through profiles, groups, node tests, and connection information, which makes it easier to diagnose the path rather than treating connectivity as an unexplained on/off switch. If that level of control fits your setup, you can compare the available clients and follow the installation guidance before importing a provider-approved subscription.

Download a Clash client →

Ready to get started?

Choose a compatible client, add your profile, and test the route that suits your everyday needs.