Adding a subscription in Clash Verge Rev is usually straightforward, but the first setup can be confusing if you are not sure which screen accepts the URL or what should happen after you click update. A subscription URL is a link that lets the client download a profile containing proxy servers and, often, routing rules. This guide explains how to add that link, refresh the profile, confirm that the imported servers are available, and troubleshoot the most common problems without exposing your account credentials.
Before You Add a Subscription
Make sure you have two things ready: Clash Verge Rev installed and a valid subscription URL from your provider. The URL is usually available in the provider’s account page or subscription panel. It may be labelled Clash, Clash-compatible, Mihomo, or Copy subscription link. If the provider offers several formats, choose the one intended for Clash or Mihomo rather than a format for a different client.
A subscription URL is not the same as a single proxy server address. It normally points to a remote configuration that can contain multiple servers, proxy groups, and rules. Clash Verge Rev downloads that configuration and stores it as a profile. When the provider changes servers or updates the configuration, refreshing the profile retrieves the latest version.
- Use the provider’s official link. A copied URL may include an account token, so treat it like a password.
- Check the client version. Labels and button positions can change between releases, but the workflow remains a profile import followed by a profile update.
- Keep the link private. Do not paste it into public chat, screenshots, issue reports, or websites that promise to “test” subscriptions.
- Start with one profile. Adding several similar links at once makes it harder to identify which profile is active and which one contains the servers you expect.
Before proceeding, confirm that the subscription has not expired and that the provider permits the device or number of connections you plan to use. A link can be syntactically correct but still return an error because the account is suspended, the traffic quota is exhausted, or the provider has disabled an older URL.
Add the Subscription URL
In Clash Verge Rev, open the Profiles page from the main navigation. The page is where remote subscriptions and local configuration files are managed. Look for an input field or control for adding a remote profile. Depending on the release, it may be labelled Download from URL, Import from URL, or simply appear beside a plus button.
- Copy the complete subscription URL from your provider’s dashboard. Use the copy button if one is available, rather than selecting only part of a long link.
- Return to the Profiles page and choose the remote URL or download option.
- Paste the link into the URL field. Check that the beginning, middle, and end of the address are present, especially if the link contains a long token or query string.
- If the dialog includes a profile name, enter a recognizable label such as the provider name or “Personal subscription.” The label is for your convenience and does not change the URL.
- Confirm the import or download action and wait for the client to finish retrieving and parsing the profile.
Do not add quotation marks around the URL, and do not insert spaces or line breaks. If the provider supplies separate links for different clients, do not assume that every link is interchangeable. A link intended for a mobile app or a different proxy format may return content that Clash Verge Rev cannot parse.
When the import succeeds, the new profile should appear in the profile list. In many versions, selecting the profile makes it the current configuration; in others, you may need to click a separate activation, use, or switch control. Check the visible selected state rather than assuming that a profile is active simply because it appears in the list.
If the application shows a download error immediately, note the message before trying again. “Timeout,” “connection refused,” and “invalid configuration” point to different causes. Repeatedly clicking the import button will not fix an expired link or malformed configuration, and it can make it harder to tell which attempt produced the current profile entry.
Refresh and Activate the Profile
A successfully imported profile is only the first step. Profiles can become stale as providers replace nodes, change server addresses, or update routing rules. To refresh one, return to the Profiles page, find the relevant entry, and use its update, refresh, or download control. Some versions also provide a context menu when you right-click the profile or open its more-options button.
Wait for the refresh to complete before switching profiles or closing the application. A successful update normally leaves the profile in the list and reports that the download or parsing finished. If the client offers automatic updates, the interval may be configurable in the profile’s options. Automatic refresh is convenient, but it does not guarantee that the subscription is usable: the URL still needs to be reachable, the account must remain active, and the downloaded file must be valid.
After refreshing, select the profile you intend to use. Then check the main control for the proxy service. Depending on your configuration, you may need to enable the system proxy, TUN mode, or another traffic-capture option before applications send traffic through Clash Verge Rev. These controls are separate from downloading the subscription. Importing a profile alone does not necessarily redirect the computer’s traffic.
To verify that the profile is active, look for a selected profile indicator and open the proxy or node view. You should see the proxy groups and, when the configuration includes them, a list of servers. Select a group and inspect its available choices. If you are unsure which node to start with, use the provider’s recommended group or node first; advanced automatic-selection groups can be explored after you confirm that the basic setup works.
| What You See | What It Usually Means | Next Check |
|---|---|---|
| Profile appears and nodes are listed | The profile was downloaded and parsed | Select the profile, choose a group or node, and enable the required traffic mode |
| Profile appears but has no visible nodes | The content may be a rules-only config, an unsupported format, or an incomplete download | Refresh once, then check the provider’s Clash-compatible link and the client log |
| Update reports a network error | The URL could not be reached or the remote server rejected the request | Check connectivity, URL validity, account status, and provider service notices |
| Nodes appear but tests fail | The profile exists, but connections may be blocked, expired, or temporarily unavailable | Try another node and review the log and provider status before changing unrelated settings |
Subscription Updates and Profile Care
Refreshing a subscription updates the remote profile that Clash Verge Rev downloaded. It is different from updating the application itself, and it is also different from updating the Mihomo core. If you are troubleshooting, identify which layer is involved: a subscription update changes profile content; an application update changes the desktop client; a core update changes the engine that processes traffic.
Use a manual refresh when you have just changed something in the provider dashboard, when a server has stopped working, or when the provider announces an update. If the application supports scheduled updates, a moderate interval is usually more useful than refreshing every few minutes. Excessively frequent requests can add load, trigger provider limits, or use up request quotas without making a stale profile more reliable.
Keep the original subscription URL in a secure place if you need to re-import the profile, but avoid maintaining multiple copies in plain text files that are synced or shared. If you rename a profile, the name generally changes only the local label. If you delete a profile, the remote account is not necessarily cancelled; subscription billing and access are controlled by the provider.
- Refresh before diagnosing old nodes. A profile that has not been updated for weeks may contain servers the provider has already retired.
- Do not overwrite a working profile blindly. If a new URL or configuration is being tested, keep the old profile until the replacement works.
- Use provider documentation for conversion links. Third-party conversion services may receive your private URL and can transform rules or server entries unexpectedly.
- Re-import only when necessary. If the existing profile refreshes normally, adding the same URL again may create duplicate entries rather than repair the profile.
Some providers distribute a subscription URL that changes after it is regenerated. If an old profile stops updating after you reset the link, replace its URL using the profile edit or re-import workflow available in your version of the client. Do not assume that refreshing an old link will automatically retrieve the new one; the client can only request the address currently stored in the profile.
Troubleshoot Missing or Unavailable Servers
If the profile is visible but servers do not appear, first determine whether the download failed or whether the downloaded configuration simply does not contain individual proxy entries. A profile can consist mainly of rules and proxy groups, and a provider may expose server entries through a format or mechanism that a particular client version does not support. Refresh once, read the notification, and inspect the application log for a parsing or download error.
When a link fails to download, check the basics in a deliberate order:
- Verify the exact URL. Compare it with the provider’s current link. Watch for missing characters, accidental spaces, copied punctuation, or an old token.
- Check the account. Sign in to the provider’s official site and confirm that the subscription is active and within its data or connection limits.
- Test ordinary connectivity. A captive portal, restrictive network, DNS issue, or temporary outage can prevent the client from reaching the subscription host.
- Confirm the profile format. Ask the provider for the Clash or Mihomo-compatible URL if several formats are listed.
- Review the error and logs. A timeout suggests reachability; a parse error suggests returned content; an authorization response suggests a link or account problem.
If servers are listed but all connection checks fail, do not immediately edit the subscription YAML. Try more than one server, check whether the system clock is correct, and look for a service notice from the provider. A failed latency test can also be caused by the test URL being unavailable from your network; it does not always prove that the proxy server itself is offline.
Make sure the active profile is the one you just refreshed. It is easy to update one entry and continue using another, especially when several profiles have similar names. Also verify that the proxy group is not set to a disabled or empty option. For a basic test, select a known available node manually, then check the client’s connection view or logs to see whether a request reaches that node.
For more useful support, share the client version, operating system, exact non-sensitive error text, and the steps that reproduce the issue. Never post the complete subscription URL, authentication token, private server address, or an unredacted profile. If a diagnostic file contains credentials, remove them before sharing it with anyone.
A Reliable First-Connection Check
Once the profile is active and a node is selected, test one application or one website before changing several settings. Confirm that the proxy service is enabled in the mode you intend to use, then watch the connection or log view while making a request. If the request appears in Clash Verge Rev, the client is receiving traffic; if it does not, the remaining issue may be the system proxy or traffic-capture configuration rather than the subscription.
Change one setting at a time. Switching system proxy mode, enabling TUN, changing DNS options, and editing rules simultaneously makes it difficult to identify what fixed or caused a problem. For a first-time setup, the provider’s default profile and recommended node are the best baseline. Once traffic works, you can adjust routing groups and application-specific behavior with a clear way to return to the known-good configuration.
The normal routine is simple: keep the URL private, refresh the correct profile when needed, confirm that it is selected, and test a node before changing advanced settings. If the profile repeatedly fails to update or contains no usable servers, the provider can confirm whether the link, account, and returned format are valid. With those checks in place, Clash Verge Rev can keep your subscription profile current without requiring you to edit every server manually.
Take Full Control of Your Traffic with Clash
Available on Windows, macOS, Linux, Android, and iOS. Flexible rules, simple setup, ready to use.