Clash Verge Rev: How to Add and Update a Proxy Subscription

What a proxy subscription does in Clash Verge Rev

A proxy subscription is a provider-issued URL that lets a compatible client retrieve a profile containing proxy servers, groups, and sometimes routing rules. In Clash Verge Rev, adding the URL creates a profile in the client; it does not automatically mean that a proxy is selected or that traffic is being routed. You may need to choose the profile, select a node in one of its proxy groups, and enable the system proxy or another supported traffic mode before applications use it.

This distinction explains many first-time setup questions. A subscription can import successfully while the browser still uses a direct connection. A profile can appear in the list but contain no usable nodes because the URL has expired or the provider returned an error page. And a node can be visible without being selected in the group that your rules actually use. Treat setup as a short sequence of checks: add the address, retrieve the profile, select it, choose a route, and verify the result.

The names and positions of controls can vary between Clash Verge Rev releases and operating systems. Look for the function described here—usually a profile or subscription area, an add control, and a refresh control—rather than relying on a screenshot from a different version. You will need an active subscription URL from a provider or a profile URL from infrastructure you manage. Keep that URL private: it can contain credentials, and anyone who obtains it may be able to retrieve or use your profile.

Prepare the subscription URL before importing

Copy the complete subscription URL from the provider’s account page or the source that issued it. Use the client’s copy button when available. If you copy it manually, check that the selection includes the full address and not an adjacent label, quotation mark, or trailing punctuation. Some subscription URLs are long and include authorization data after a question mark; trimming that portion can make the address look plausible while causing the request to fail.

Do not paste the address into a public chat, issue tracker, screenshot, or document shared with people who do not need access. If you ask for support, redact the value rather than showing even a shortened token that might remain valid. Avoid testing a subscription by opening it in an unfamiliar third-party website. A profile file may reveal server information, provider metadata, or access credentials, so handle both the URL and any downloaded configuration as sensitive data.

It is also useful to confirm that the subscription is intended for a Clash-compatible client. Providers may offer separate links for different applications, formats, or devices. If the provider’s page gives a specific Clash or Mihomo subscription option, choose that one. A web dashboard address, account login link, or single-node connection string is not necessarily a subscription URL. When uncertain, check the provider’s setup instructions instead of repeatedly importing different addresses.

• Check access: confirm that the account or plan is active and that the provider has not revoked or rotated the link.
• Check format: use the Clash-compatible subscription option, not a link intended for a different protocol client.
• Check copying: preserve the entire address, including any query parameters required for authorization.
• Protect credentials: treat the URL like a password and redact it before sharing diagnostic details.

Add the subscription profile in Clash Verge Rev

Open Clash Verge Rev and go to the area used to manage profiles or subscriptions. Depending on the build, the section may be labelled Profiles, Subscriptions, or with a similar term. Choose the control for adding a remote profile. If the application presents multiple import choices, select the option that accepts a URL rather than a local file, then paste the address into the URL field.

Before saving, check that the field contains the intended subscription address and that you have not pasted a newline or leading space. If the dialog offers a profile name or remark, use a short label that helps you recognize the provider or account later. This label is for your own organization; it does not change the subscription contents. Avoid putting sensitive account details in the label if the application window may be visible during screen sharing.

Save or confirm the new entry. The client should then request the profile from the provider. Depending on the network and the provider’s response time, the import can take a little while. Allow the request to finish before clicking repeatedly. If the interface reports an error, note the general message and check the URL, network access, and subscription status. Do not publish a screenshot until you have verified that the complete URL and any identifying profile data are hidden.

A successful import typically creates a profile entry in the list. It may not immediately become the active profile. Select the newly added entry if the client does not do so automatically, and confirm that it is marked as current or active. If the entry is visible but has no proxy groups or nodes, importing the URL alone has not proved that the provider returned a usable configuration; continue with the refresh and troubleshooting checks below.

Refresh the profile, then select a usable node

Profiles are snapshots of configuration data retrieved from the subscription source. Providers can update server addresses, remove unavailable nodes, or change group membership, so an existing entry may need to be refreshed. In the profile list, use the refresh or update control associated with the relevant entry. If there is a global refresh control, first make sure you understand whether it updates one profile or every remote profile in the list.

After refreshing, wait for the operation to complete and inspect the profile again. Look for a timestamp, completion notice, or updated node list if the interface provides one. A refresh that fails should not be treated as a successful update simply because the profile entry remains visible. Keep the error message, but avoid copying a full URL or secret response into a public support post.

Next, open the proxy or group selection view. The profile may contain groups such as an automatic selection group, a regional group, or a group with a manually chosen node. Select a suitable node in the group that your traffic will actually use. A node shown in the profile is not necessarily the node currently selected. If the group offers a delay test, use it as a rough connectivity signal, not a guarantee of speed or availability for every site.

Finally, check the client’s operating mode and traffic controls. Rule mode applies the profile’s routing rules; Global mode sends more traffic through the selected proxy group, and Direct mode bypasses proxy routing. The exact behavior depends on the configuration. Enable the system proxy only if you want applications that respect the operating system’s proxy settings to use Clash Verge Rev. Some applications may require another supported mode or may not follow system proxy settings at all.

Fix failed imports and profiles with missing nodes

If the import fails immediately, begin with the least disruptive checks. Confirm that the address is complete, that the subscription is still active, and that your device can reach the provider. If the provider offers a dashboard, check whether it reports a subscription reset, account limit, or service incident. A browser successfully opening the provider’s website does not necessarily prove that the subscription endpoint is reachable; the endpoint may use a different host or require authorization.

If the profile imports but displays no nodes, consider whether the provider returned an error page, an empty profile, or data in a format the client cannot use. Re-copy the Clash-compatible URL from the provider account page rather than reusing a link from an old note. Refresh once after confirming the address. If the provider has recently changed its profile format or endpoint, follow its current client-specific instructions; repeatedly refreshing a stale link will not restore nodes that the provider no longer publishes.

When a refresh hangs or fails intermittently, separate a client problem from an upstream availability problem. Check whether the same URL works on another trusted network, such as a different Wi-Fi connection, without sending it to a third-party checker. A temporary network interruption, DNS issue, provider outage, expired account, or local security software can all interrupt retrieval. If you have multiple profiles, update only the one you are diagnosing so you can identify which request failed.

If the nodes appear but tests fail, do not assume the import itself is broken. A node may be offline, overloaded, or incompatible with the network you are currently using. Try another available node, check the client’s connection or log view for the failing destination, and verify that the chosen proxy group is not set to a different node than the one you tested. If all nodes fail, ask the provider whether the subscription is active and whether there is a service issue. Share only the error text and relevant timestamps, with tokens, addresses, and account identifiers removed.

Keep subscriptions private and current

A subscription profile may update automatically on a schedule, or it may require a manual refresh. Check the profile’s own update settings if you want to know which behavior applies. Avoid setting an unnecessarily aggressive refresh interval: frequent requests can create noise, consume provider resources, or trigger account protections. If a provider specifies a recommended update interval, follow it. When you need to troubleshoot a change, record the approximate time of the last successful refresh so you can distinguish stale data from a new import failure.

If your provider issues a replacement URL, add or replace the profile using the new address and confirm that the new entry works before removing the old one, when the provider permits that approach. Once verified, delete obsolete entries so you do not accidentally select a stale profile later. If a URL is exposed publicly or sent to the wrong person, treat it as compromised and use the provider’s account tools to reset or revoke it. Merely removing the entry from your local client does not invalidate a URL that remains active on the provider’s side.

For everyday use, keep the workflow simple: select the intended profile, refresh it when needed, choose a working node in the correct group, and confirm the traffic mode. If a web page fails, check the active route before changing the subscription itself. This small distinction saves time because profile retrieval, node availability, and application routing are separate parts of the connection path.

Some single-purpose proxy apps make it easy to connect quickly, but they may offer less visibility into profile refreshes, groups, and rule-based routing. Clash Verge Rev puts those pieces in one place: you can inspect the imported profile, update it, choose among its groups and nodes, and check how traffic is handled. If that level of control fits your setup, you can compare supported clients and get the version for your platform on the download page.

Download Clash →