How To Add a Proxy Subscription in Clash Verge Rev

Before You Add a Subscription: Get the Right Link

In Clash Verge Rev, a subscription is a remote source from which the client downloads a proxy configuration. Depending on your provider, that configuration may contain proxy nodes, proxy groups, routing rules, DNS settings, and other options. The client stores the downloaded profile and uses it with its configured core; adding a subscription does not, by itself, connect your computer to a proxy.

First, sign in to your provider’s account page and look for a link specifically intended for Clash, Clash Meta, or mihomo. Providers may call it a subscription URL, subscription link, or configuration link. A generic link for a different client may return a format that Clash Verge Rev cannot use. If you are unsure which format to choose, check the provider’s instructions rather than trying links at random.

Clash Verge Rev uses the mihomo core to process compatible configurations. Provider profiles can still differ in their supported features, and a client update does not make every possible configuration valid. If the provider offers several formats, choose one documented for Clash or mihomo.

Add the Remote Profile in Clash Verge Rev

The exact button labels can differ slightly between Clash Verge Rev releases and operating systems, but the usual workflow is on the Profiles page. Add a remote profile, enter its URL, give it a recognizable name, and then download it. If you see a choice between a remote profile and a local profile, choose the remote option for a subscription link.

  1. Open Clash Verge Rev. Wait for the main window to finish loading. If the app asks to install or update a core, complete that step before troubleshooting profile content.
  2. Open Profiles. Look for an add, new, or remote-profile control on that page. The wording and position may change across releases, so identify the action by its purpose rather than relying only on one screenshot.
  3. Choose the remote option. Enter the full subscription URL in the URL field. If the dialog also asks for a profile name, use a short label such as “Personal subscription” or the provider’s name.
  4. Set an update interval only if needed. Some versions expose an auto-update interval in the add-profile dialog or profile settings. Use the provider’s recommended interval, or leave automatic updates off if you prefer to refresh manually. An update interval is not a promise that the provider will always be available.
  5. Save the profile and start its first download. Depending on the release, saving may begin the download automatically, or you may need to select the profile and choose an update or download action. Wait for the request to finish before changing pages.
  6. Select the downloaded profile. A profile can appear in the list without being the active configuration. Click or select the profile and use the available activate or switch action if the interface shows it.

Give the profile a useful name, especially if you may add more than one. Names such as “Subscription 1” are hard to distinguish when troubleshooting. Avoid putting the full subscription URL in the name, because the URL may contain account-specific information.

Once the download completes, check that the profile is selected and that its details show a recent update time or a successful status. If the profile list is empty, the download is still running, or an error appears, don’t assume the profile is active just because you saved the URL.

Download, Activate, and Check the Profile

Adding the URL creates an entry in the client; downloading retrieves the current configuration; activating tells Clash Verge Rev which profile to use. These are separate steps in some versions of the interface. After the first download, confirm the profile is the active one before testing a connection.

Next, open the proxy or groups view and check whether proxy entries and policy groups have appeared. A profile that contains only proxy nodes may have a simpler group layout than one supplied as a complete configuration. The names of groups and nodes come from the provider, so they may not match labels shown in tutorials. Select a usable node or a suitable selection group if the profile requires manual selection.

Then check the client’s operating mode and traffic routing controls. In Rule mode, traffic is routed according to the profile’s rules; in Global mode, traffic is generally sent through the selected global policy; and Direct mode bypasses proxy routing. The system proxy and TUN controls determine how applications send traffic to the core, while the rules and proxy groups determine what the core does with traffic it receives. One setting does not replace the others.

For an initial test, choose one node, use the same browser and network you normally use, and open a site that should follow the chosen route. If the client has a connection log, check whether the request appears and which rule or policy handled it. This helps distinguish an inactive system proxy from a profile or node problem.

Be cautious when using TUN during the first setup. TUN routes traffic through a virtual network interface and may require additional permissions or service setup. First verify that the profile downloads and works with the simpler system proxy workflow, if that is suitable for your operating system. Enable TUN later only if you need it, and avoid running two clients that both try to control the system proxy or TUN at the same time.

Refresh the Subscription Later

A remote profile is a downloaded snapshot until it is refreshed. Providers may change nodes, credentials, rules, or configuration structure over time, so a profile that worked last week may need an update. On the Profiles page, select the profile and use the update, refresh, or download action shown by your version of Clash Verge Rev. Wait for the operation to finish, then confirm the displayed update time or status changed.

If automatic updates are available, choose an interval that suits your provider’s guidance. Frequent polling usually does not make nodes faster or improve availability; it only asks the provider for a new profile more often. If you rely on manual updates, refresh after the provider announces a configuration change or when a profile-specific issue suggests that its contents may be out of date.

An update can replace the downloaded content without changing the subscription URL. It may also change nodes or provider-supplied rules. Before editing a profile directly, check whether your changes are stored as a separate override or are part of the remote content. If an update removes a change you made, don’t repeatedly edit the downloaded profile; look for a supported local override workflow in the client and keep a backup of important custom settings.

  1. Open the Profiles page and identify the subscription you want to refresh.
  2. Run the profile’s update or refresh action and wait for a success message or updated timestamp.
  3. Check whether the profile remains selected after the update; switch to it again if required.
  4. Review proxy groups and test one connection, especially if the provider changed the profile.
  5. If the update fails, record the message and time before trying again. Repeated retries can obscure whether the provider or your network is responding differently.

Some providers limit how often a subscription can be fetched. If you receive a rate-limit or quota message, pause and check the provider’s account page or documentation instead of refreshing repeatedly. If you use the same subscription on multiple devices, each device may make its own update request; check the provider’s simultaneous-use and request limits.

When a profile cannot be added or refreshed, start with the URL and the provider response. A message such as “invalid URL” may indicate a malformed address, while a timeout points more often to network reachability. A server can also respond with an authentication error, an expired-link notice, or a rate limit. The exact text varies, so use it as a clue rather than assuming every failure has the same cause.

If the URL downloads successfully but Clash Verge Rev reports a parse or configuration error, the server may be returning content that is not valid for the selected profile format or core. Ask the provider whether the profile is intended for mihomo and whether it uses features that require a particular core version. Updating the client or core can help with compatibility, but it will not fix a truncated response, an expired subscription, or invalid YAML.

If the profile updates successfully but traffic still fails, return to the basics: confirm that the profile is active, select a node or group, check the operating mode, and verify that the application’s traffic reaches Clash Verge Rev. Use the connection log to see whether a request was received and which rule handled it. Change one setting at a time so you can tell which change affected the result.

For a fresh installation, begin with the standard import workflow and avoid combining several changes at once. Once the profile updates and a basic connection works, you can configure custom rules, startup behavior, or TUN if your setup needs them. If you still need the installer or a separate setup walkthrough, use the site’s download page or getting started guide.

Download Clash