Clash Verge Rev can use a subscription URL to download a profile containing proxy nodes, proxy groups, and routing rules. Adding that URL is only the first step: you still need to make the profile active, select an available node or policy group, and confirm that traffic is actually reaching the proxy core. The exact labels and layout can vary between Clash Verge Rev releases, but the general process is the same.
A subscription URL is also sensitive account information. It may contain a token that grants access to your service configuration, so treat it like a password: do not post it in screenshots, chat messages, public issue reports, or configuration examples. If it is exposed, ask the provider whether the link can be reset or regenerated.
How to Add a Proxy Subscription in Clash Verge Rev
Understand what a subscription URL imports
A subscription URL is an address that Clash Verge Rev uses to retrieve configuration data from a provider. Depending on the service, the downloaded content may be a complete YAML profile, a list of proxy nodes, or data formatted for a particular client or conversion service. The subscription provider—not Clash Verge Rev—controls which nodes, groups, rules, and options appear in the result.
In the client, a subscription is normally represented by a profile. A profile is the configuration that the core can load at runtime. It is different from an individual proxy node: one profile can contain many nodes and several policy groups, while a node is one possible outbound connection. It is also different from a proxy provider in a YAML configuration. Proxy providers are configuration components that can load node lists dynamically; adding a subscription URL through the graphical profile manager generally creates or downloads a client profile, not necessarily a proxy-providers entry that you can edit independently.
Before importing anything, check the provider’s instructions for the expected link type. Some services offer separate links for Clash-compatible clients, sing-box, or other formats. A browser-friendly dashboard URL, account sign-in page, or one-time purchase link is not necessarily a usable subscription. If the service offers a copy button labelled for Clash, Mihomo, or a compatible client, use that specific URL.
| Item | What it means | What to check |
|---|---|---|
| Subscription URL | The private address used to retrieve provider data. | Copy the complete link, including its scheme and token, and keep it private. |
| Profile | The downloaded configuration that Clash Verge Rev can activate. | Confirm that it imported successfully and is selected as the active profile. |
| Node or group | A specific proxy or a policy that chooses among proxies. | Choose a usable entry after the profile has loaded. |
Prepare Clash Verge Rev before adding the link
Install and open Clash Verge Rev from a source you trust, then let the application finish starting its proxy core. If the client displays a first-run prompt to install or prepare a core, complete that step before importing a profile. The interface can download and display configuration data without necessarily proving that a compatible core is ready to run it.
Check that another proxy client is not already controlling the system proxy or occupying the local ports that Clash Verge Rev needs. Running multiple clients at the same time can produce misleading results: one application may set the operating system proxy while another owns the listening port, or a previously enabled client may continue intercepting browser traffic. If you are switching from another client, turn off its system proxy and TUN mode before testing the new setup.
It is also useful to confirm that the computer has a working internet connection before importing. Open the provider’s account page or check its service status using the normal connection. If the provider’s site is unavailable, the subscription URL may fail to download even though Clash Verge Rev itself is functioning correctly. Conversely, if the provider dashboard works but the subscription request fails, the link may be expired, copied incompletely, or intended for a different client format.
Do not paste the URL into a public search engine, a third-party “subscription checker,” or an online converter unless the provider explicitly recommends that service and you understand what it receives. These tools may log the full token. A safer first test is to add the URL directly in Clash Verge Rev and inspect the client’s own import result and logs.
Add the subscription URL
Open the profile management area in Clash Verge Rev. Depending on the installed release, it may be labelled Profiles, Subscriptions, or something similar. Look for an action to add a remote profile, add from URL, or create a subscription. Avoid choosing a local-file import action unless the provider gave you a configuration file to download manually.
- Copy the provider’s Clash- or Mihomo-compatible subscription URL from its account page.
- In Clash Verge Rev, choose the action for adding a remote profile or subscription.
- Paste the complete URL into the address field. Do not omit characters after a question mark, ampersand, or other URL separator.
- Enter a short local name, such as the provider name or “Main profile.” The name is only a label in the client; it does not change the subscription data.
- Save or confirm the entry, then wait for the initial download and parsing to finish.
If the dialog offers optional fields such as a file name, update interval, or request headers, use the provider’s documentation rather than guessing. A standard subscription often needs only the URL and a local label. Extra headers or conversion parameters can change how a server responds, and an invented value may cause the service to reject the request.
After the import, check for a success state and open the new profile’s details if available. A profile name appearing in the list does not by itself prove that the content downloaded successfully. Look for a recent update time, a count of available proxies, or a readable configuration preview. If the profile is marked invalid or has no usable entries, do not immediately edit the downloaded YAML: first check the URL, provider format, and error message.
For a subscription that was saved but not activated automatically, select it as the current profile using the client’s profile controls. Some releases distinguish between downloading a profile and switching to it. A successfully downloaded profile that is not active cannot determine the routes used by the running core.
Activate the profile and choose a node
Once the profile has loaded, activate it in the profile list if the client has not already done so. Then open the proxy or group view. A configuration commonly organizes individual nodes inside groups with names such as “Proxy,” “Auto,” “Select,” or a region label, but group names are chosen by the provider and can differ substantially. Do not assume every profile has a group called “Proxy.”
For an initial test, choose a policy group that lets you select an individual node, if one is available. If the provider includes an automatic latency group, it can be convenient for normal use, but it may choose a different node from the one you expect. A manual selection makes the first diagnosis easier because you know which outbound entry is being tested. Select a node whose name corresponds to a location or service you are allowed to use, then wait for the UI to show that the choice has been applied.
Some group entries are not direct nodes. An entry may point to another group, use automatic selection, or direct traffic without a proxy. If a group contains only nested groups, open the relevant group and make a selection there. The relationship is defined by the downloaded configuration; the client cannot create a missing node simply by changing the group selection.
Use the client’s delay or connectivity test as a first check, but interpret its result carefully. A latency test usually measures whether the core can reach a test endpoint through the selected node. It does not prove that every website, application, DNS request, or rule will work. A successful delay result paired with a failed website test may point to a routing rule, DNS behavior, or application proxy setting rather than a broken subscription.
Verify that a connection uses the profile
Turn on Clash Verge Rev’s system proxy switch if you want applications that respect the operating system proxy to use the client. The switch and the active profile do different jobs: the profile supplies the rules and proxy entries, while the system proxy setting directs compatible applications to the local proxy listener. A green system-proxy indicator alone does not confirm that the selected node is reachable.
Open a test website or application, then inspect the client’s connection list or logs. Look for the destination, the matched rule, and the policy group or proxy shown for the connection. If the request appears there, it reached the running Clash core. If a browser loads the page but no corresponding connection appears, the browser may be using a separate extension, its own proxy configuration, another VPN, or an already established connection.
To test a command-line program, confirm the actual local port shown in the client rather than assuming it is always 7890. Ports can be changed by the user, a profile, or another application. A mixed port commonly accepts both HTTP and SOCKS5 proxy requests; if your client shows a mixed port of 7890, a simple request can be tested with:
curl -x http://127.0.0.1:7890 https://example.com/ -I
Replace the port with the one displayed by your client. If the request succeeds but a particular application does not, that application may ignore system proxy settings and require its own proxy configuration. If the request cannot connect to the local address, check whether the core is running and whether the port is listening before changing nodes.
For a useful verification, compare at least two signals: a successful request through the intended application and a matching connection entry in Clash Verge Rev. An IP-check website can show the apparent exit address, but it does not reveal whether every request is routed the same way. Rules may send different domains directly, through different groups, or to a reject policy.
Refresh the subscription and protect its URL
Providers can change nodes, credentials, group names, and routing data over time. Use the profile’s update or refresh action to retrieve the latest version. A manual refresh is useful after the provider announces a change or when a node that worked earlier stops connecting. Wait for the request and parsing to finish, then check the displayed update time or result. Repeatedly clicking refresh while a download is still running can make it harder to tell which request produced the current state.
If the client provides an automatic update interval, choose a value based on the provider’s instructions. Very frequent polling is rarely necessary and may trigger service limits. A short interval also cannot make an unavailable server respond faster. If the provider specifies a refresh schedule or traffic limit, follow it rather than setting the most aggressive interval offered by the UI.
After an update, review the profile and group list again. Node names may change, a manual selection may no longer exist, or the provider may replace a group. If the active choice has disappeared, choose a currently available node. Avoid modifying the downloaded subscription file directly unless you know how the client handles local edits; the next update may overwrite them. Use a supported override or merge feature for persistent local changes.
Protect the URL as you would a credential. Do not include it in public bug reports, screenshots, screen recordings, shell history, or a shared configuration backup. If a diagnostic report is needed, redact the full token and any query values while preserving the general error text. Store exported profiles in a private location because they may include node addresses, authentication parameters, or other account details.
Diagnose common import and connection problems
When an import fails, use the error stage to narrow down the cause. A network timeout points toward reachability or server availability; an authorization response may indicate an expired link or account limit; a parsing error suggests that the returned content is not in a format the installed core can load. Do not treat all of these as node failures, because the node list may not have been downloaded yet.
| Symptom | Likely cause | Practical check |
|---|---|---|
| The URL request times out | The provider endpoint is unreachable, the network blocks the request, or the service is temporarily unavailable. | Check the provider’s status and retry from a working network without sharing the URL with a checker. |
| The server rejects the request | The link is expired, incomplete, copied from the wrong account, or subject to a service limit. | Copy a fresh Clash-compatible link from the provider dashboard and review account notices. |
| The response cannot be parsed | The link returns a web page, an incompatible format, or configuration syntax unsupported by the active core. | Confirm the link type and inspect the client log for the parsing error; check the core version if the configuration uses newer fields. |
| The profile loads but shows no usable nodes | The provider returned an empty list, the wrong profile type was selected, or the configuration references unavailable providers. | Refresh once, review provider instructions, and confirm the expected client format. |
| Nodes appear but traffic fails | The profile may be inactive, the selected node may be offline, or the app’s traffic may not enter the core. | Activate the profile, test another available node, and inspect the connection log for the target request. |
If the profile imports but the core fails to start, read the startup log before replacing the subscription. A YAML field unsupported by the installed core, a missing proxy-group reference, or a port conflict can prevent runtime startup even when the subscription download itself succeeded. If the log names a specific field, check whether the client is using Mihomo or another core and whether that core version supports the field.
When asking the provider or client community for help, report the client version, core name and version, operating system, approximate time of the failure, and the non-sensitive error message. Remove subscription tokens, server credentials, and private node details from logs and screenshots. This preserves the information needed for diagnosis without exposing account access.