A proxy subscription is a URL that lets Clash Verge Rev download and manage a provider’s proxy profile. Once imported, the profile can contain multiple nodes, proxy groups, and routing rules; you then choose a node or group in the client rather than entering each server manually. This guide walks through adding the subscription, refreshing it, selecting a route, and checking that traffic is working. It also covers common import failures and practical ways to keep the subscription URL private.

Before You Import a Subscription

First, make sure you have a subscription link from a provider you trust. It is usually an HTTPS URL, sometimes with a long random-looking path or query string. Treat the entire link like a password: anyone who obtains it may be able to download your profile or use your account, depending on how the provider manages access. Do not post it in a support forum, screenshot it with the address visible, or paste it into an online URL checker.

Clash Verge Rev is a graphical client for a Clash-compatible core, commonly Mihomo. The client interface and the core do different jobs: Verge Rev stores and displays profiles, while the core parses the downloaded configuration and runs the proxy service. A subscription may import successfully but still fail to run if its format requires features that are unavailable in the selected core version. If the provider specifies a supported client or core, check that information before troubleshooting the URL.

Before starting, confirm the following:

  • You have copied the complete subscription URL, not a browser page address or a one-time login link.
  • Your device has an internet connection that can reach the provider’s subscription host.
  • You have installed a current Clash Verge Rev release from a source you trust.
  • You know where the client’s profile list and subscription update controls are located. Labels may differ slightly between releases.
Protect the URL: A subscription link can grant access to your service. If you accidentally share it publicly, contact your provider and ask whether it can be renewed or revoked.

Import the Subscription URL

In Clash Verge Rev, subscriptions are generally added as remote profiles. Open the profile or subscription management area, then look for an action such as New Profile, Import from URL, or an add button. The exact wording and location can vary by version, so use the profile page rather than the system proxy settings if the interface looks different.

  1. Open Clash Verge Rev and go to the page that lists profiles.
  2. Choose the option to add a profile from a URL or subscription link.
  3. Paste the complete URL into the address field. Avoid adding quotation marks, spaces, or line breaks before or after it.
  4. Enter a recognizable profile name, such as the provider’s name or “Personal subscription.” Use a label that does not expose private account details if other people can see your screen.
  5. Confirm the import and wait for the client to fetch and parse the profile.

If the client offers an option to save the profile as a remote subscription, keep that option enabled. A remote profile retains the source URL so that the client can download newer configuration data later. Importing a local file instead creates a different workflow: it may work for a one-time YAML file, but it will not necessarily refresh itself from the provider.

Some providers offer both a subscription URL and a configuration download button. Use the subscription URL when you want ongoing updates. If you only have a file, download it from the provider’s official account page and use the client’s local-file import option. Do not rename a text document to YAML unless its contents are actually a valid Clash-compatible configuration.

Check before saving: If the provider supplies separate links for different client types, use the Clash, Mihomo, or Clash-compatible link. A link intended for another application may return a different format that Clash Verge Rev cannot parse.

Refresh and Activate the Profile

After adding the URL, the profile should appear in the profile list. Select it and use the refresh or update control to fetch the latest version. Wait for the operation to finish before switching to another profile. A successful download usually updates a timestamp, status indicator, or profile details, although the exact feedback depends on the release.

Next, make the imported profile active. Many versions use a check mark, selection control, or profile card action to identify the current configuration. Selecting a profile is not always the same as starting the core or enabling the system proxy. If the interface has separate controls for the active profile, core service, and system proxy, confirm each one that you intend to use.

Profile refreshes can replace data downloaded from the provider. Avoid editing a remote profile directly unless you understand how the client handles local changes. A later update may overwrite those edits, or the profile may be generated from a subscription template that is intended to remain under provider control. If you need custom routing, use the client’s supported override or merge options where available, and keep a backup of any important local configuration.

Hands-On: Select a Node and Test Traffic

Once the profile is active, check that it contains usable proxy nodes or groups. Open the proxy or group view. A provider may present individual locations, automatic selection groups, or service-specific groups. A group can contain nodes without being a node itself: selecting the group may open another list in which you choose a member. If you see no entries, first check whether the profile finished downloading and parsing.

  1. Choose a proxy group. Start with a general group such as “Proxy,” “Global,” or an automatic selection group if the provider supplies one. Names vary; follow the provider’s documentation when available.
  2. Select a member. If the group is manual, choose one node. If it is an automatic test group, allow the client to run its checks and select a result. A displayed latency is a measurement to a test endpoint, not a guarantee that every website or application will be reachable.
  3. Enable the intended traffic mode. Rule mode is suitable for profiles that route traffic according to their rules. Global mode sends most traffic through the selected proxy group, while direct mode bypasses the proxy. Avoid changing modes without understanding how that affects local and private network access.
  4. Start the core and enable the system proxy if needed. These controls may be separate. The core handles connections; the system proxy setting tells compatible applications to use it. TUN mode, when supported and configured, handles traffic differently and may require additional permissions.
  5. Test a real request. Open a site or application that should use the proxy, then check the client’s traffic or connection view. Look for the destination, matched rule, and selected group or node. A successful latency test alone does not confirm that your device’s applications are using the proxy.

For a first test, change only one thing at a time. For example, select a single node, leave the profile’s rules unchanged, and test a site that you know should be routed through the proxy. If it works, test another application. If it does not, inspect the client’s connection log before switching several settings at once; otherwise it becomes difficult to tell which change affected the result.

What You SeeWhat It Usually MeansWhat to Check
Nodes appear, but there is no trafficThe profile is loaded, but the application may not be using the proxyCore status, system proxy or TUN setting, and routing mode
Connections appear as directA rule may send the destination directlyMatched rule, rule mode, and the provider’s routing design
Latency is unavailableThe test endpoint may be unreachable or the test has not completedSelected node, test URL, network access, and provider status
Some apps work and others do notApplications can use different proxy mechanisms or bypass system settingsApplication proxy support, TUN configuration, and connection details

Update Schedule and Subscription Hygiene

Providers may change node addresses, credentials, routing groups, or available locations. Refreshing the profile downloads the provider’s current version; it does not necessarily mean that Clash Verge Rev will update it continuously in the background. If the client exposes an update interval, choose a reasonable value based on the provider’s instructions. Frequent requests are usually unnecessary and may trigger rate limits. If no schedule is configured, refresh manually when the provider announces changes or when the current profile stops working.

When a refresh fails, distinguish a temporary download problem from a profile parsing problem. A network timeout or HTTP error means the client may not have received the profile at all. A parse or configuration error means it received data but could not interpret it as a usable configuration. The first calls for checking access to the provider and the URL; the second calls for checking the link type, profile format, and core compatibility.

Keep the subscription URL in the client’s profile manager rather than copying it into notes, chat messages, or command history. If you need a backup, use a secure password manager or another storage method with access controls. Be cautious when exporting profiles: depending on the client and provider format, an exported file may contain credentials, server details, or the original subscription address. Review the export before sharing it or attaching it to a bug report.

For troubleshooting, share the smallest useful amount of information. You can report the client version, operating system, approximate time of the error, and a redacted message. Remove URL tokens, account identifiers, passwords, UUIDs, server names if sensitive, and any authentication headers. Screenshots should be checked for the same information, including address bars, profile details, and notifications.

Troubleshoot Failed Imports

If the import does not complete, work through these checks in order. Start with the source and the URL before changing core settings. A valid proxy subscription cannot be fixed by toggling the system proxy, and a valid client installation cannot make an expired or mistyped link work.

  • Verify the copied URL. Re-copy it from the provider’s official dashboard. Check that the first and last characters are present and that no whitespace or punctuation from surrounding text was included.
  • Confirm that the link is current. Some providers let users regenerate or revoke a subscription. An old link may return an authorization error or an empty response. If so, use the current link from the account page.
  • Check network access. Try again on a stable connection, temporarily disable a captive portal if one is present, and confirm that the subscription host is reachable from your network. A timeout can be caused by DNS, a local firewall, or the provider’s server.
  • Look at the returned content, not just the URL’s appearance. A browser landing page, sign-in page, or error message is not a valid proxy profile. Do not paste a private URL into an untrusted online tool to inspect it. Use the provider’s official instructions or contact its support team.
  • Check format and compatibility. A provider may offer different subscription formats. Choose the one intended for Clash or Mihomo, and update Clash Verge Rev or its core only through a trusted release source.
  • Read the client’s error details. Record whether the failure says download, HTTP, parsing, or configuration. These clues narrow the cause and are more useful than repeatedly deleting and re-adding the profile.

If the profile imports but contains no nodes, ask the provider whether the account is active and whether the chosen subscription format includes proxy entries. If it parses but the core refuses to start, inspect the configuration error and verify support for any required features. Avoid pasting a full profile into a public issue: even when the subscription URL has been removed, the file can contain credentials or infrastructure details.

Once the profile is imported, updated, and tested, you can leave the provider’s rules and groups in place while selecting the route that fits your use. Keep the URL private, refresh only as needed, and use the connection view to confirm what the client is actually doing. If you are setting up Clash Verge Rev for the first time, a platform-specific setup guide can help you check the remaining system proxy or TUN permissions without changing the subscription itself.