Clash Verge Rev Subscription Setup: Add and Update Profiles

Before you add a subscription

A subscription is a private URL that lets Clash Verge Rev download a proxy configuration and refresh it later. You normally add the URL once, select the resulting profile, and update it from the Profiles page when you need the provider’s latest servers or rules. The subscription URL is not a proxy node by itself, and importing it does not automatically send your device’s traffic through a proxy.

Before starting, obtain a Clash-compatible subscription URL from your service provider. It may be labeled “Clash,” “Clash Meta,” “mihomo,” or “configuration URL” in the provider’s dashboard. A regular website address, account login page, or single-node share link is not necessarily a subscription. If the provider offers several formats, choose one intended for Clash or mihomo, which is the core commonly used by Clash Verge Rev.

Copy the complete URL, including its scheme such as https://. Avoid adding spaces before or after it.
Check whether the provider requires an account login, an allowlisted IP address, or a separate subscription token.
Use the provider’s current URL rather than a link copied from an old message. Subscription links often contain credentials and may be revoked or replaced.
Keep the URL private. Anyone who can use it may be able to access the subscription or consume the associated account quota.

Clash Verge Rev’s labels and button placement can differ between releases, and translated interfaces may use slightly different wording. The steps below refer to the profile-management area commonly labeled Profiles. If an exact button name does not appear, look for the control that adds a remote profile or imports a URL rather than changing unrelated core settings.

Add the subscription as a remote profile

Open Clash Verge Rev and select Profiles in the sidebar. This page lists configurations that the client can use. It may be empty on a new installation, or it may already contain a local configuration or a profile that was added earlier. A remote subscription and a local file are different sources: the remote profile can be refreshed from its URL, while a local file is edited or replaced on your device.

Open Profiles and choose the add or import control. Depending on the release, this may appear as a plus button, an import button, or a menu with an option for a remote profile.
Select the option for a URL or subscription. Do not choose a local-file option unless you have already downloaded a configuration file and intend to import that file.
Paste the complete subscription URL into the address field. If there is a separate name field, enter a short label such as Personal or Work. A clear label makes it easier to identify the profile later.
Confirm the addition or download. The client must be able to reach the provider’s server to retrieve the configuration. Wait for the profile to appear in the list and for any loading indicator to finish.
Select the new profile if the client does not activate it automatically. Look for a check mark, highlight, or active-profile indicator; the selected profile is the configuration the core will use.

Some releases may let you set a profile name, update interval, or other metadata while adding the URL. A name is only a local label; changing it does not alter the subscription’s contents. An update interval, when available, controls how often the client attempts a refresh. It does not guarantee that the provider has published new nodes, and it is not a substitute for checking whether the profile is currently active.

After importing, confirm that the profile contains usable proxy entries or policy groups. Depending on the provider’s configuration, the list may show named nodes, groups such as an automatic selection group, or both. Seeing a profile in the list only confirms that the client has a profile record; it does not prove that a proxy server is reachable or that applications are using it.

Refresh and manage profiles

A profile refresh asks the subscription server for an updated configuration. It may add or remove nodes, update policy groups, or change rules according to the provider’s current data. Refreshing normally does not change the subscription account itself. It also does not guarantee that your active node will change: the existing selection may remain selected if it is still present.

Refresh a profile manually

On the Profiles page, find the profile you want to update and use its refresh control. This is often shown as a circular-arrow icon or an update action in the profile’s menu. If the client asks which profile to refresh, select the correct one by its name. Wait for the request to finish, then check whether the profile’s update time or node list has changed.

If you have several profiles, refresh the one you intend to use rather than assuming that a global refresh control targets every entry. Keep names distinct, especially if you have personal, work, and test subscriptions. Before removing an old profile, confirm that it is not the one currently selected and that you no longer need its local settings.

Keep profile types clear

Remote subscription: Has a provider URL and can usually be refreshed from the Profiles page. The provider controls the content delivered by that URL.
Local configuration: Stored on the device and generally updated by importing or editing a file. Do not expect a refresh button to fetch provider data unless a remote source is configured.
Active profile: The configuration currently selected by the client. Having several profiles saved does not mean they are all active at once.

A subscription can also be valid while containing settings the installed core cannot parse. Clash Verge Rev commonly uses mihomo, but available fields and protocols depend on the actual core build and the configuration supplied by the provider. If a profile imports but reports a parsing error, record the error text and the client and core versions before changing settings. Avoid editing a provider-managed configuration until you have a backup, because a later refresh may replace local changes.

Select a node and enable proxying

Adding and selecting a profile is only part of the setup. You also need a usable policy or node and a traffic-capture method. In a typical desktop setup, the system proxy directs applications that respect the operating system’s proxy settings to Clash Verge Rev. TUN mode can capture more traffic, but it is a separate feature with additional permissions and routing considerations. Start with the system proxy unless you have a specific reason to configure TUN.

Open the profile’s proxy or policy-group view. The exact sidebar label may be Proxies or similar.
Choose an appropriate policy group, then select a node inside it. A group may offer options such as manual selection, automatic testing, or load balancing; these are group behaviors, not individual server protocols.
Use the client’s latency or connectivity test if available. A test result checks reachability to a chosen test address at that moment. It does not prove that every website, application, or UDP connection will work.
Open the dashboard or general settings and turn on System Proxy. Approve an operating-system permission prompt if one appears.
Visit a service that should use the selected route, and check the client’s connection list or logs to confirm that the request reaches the core.

Keep the operating mode and traffic capture separate in your troubleshooting. Rule mode applies the configuration’s rules to traffic that reaches the core; it does not capture applications on its own. Global mode usually sends captured traffic through the selected global policy, while Direct mode routes captured traffic directly. The system proxy or TUN determines which traffic enters the core; the mode and rules determine how that traffic is handled.

If a browser works but another application does not, first check whether that application honors the system proxy. Some desktop apps, command-line tools, games, and background services use their own network settings. TUN may help capture applications that do not use the system proxy, but it is not required for ordinary browser proxying and may conflict with other VPNs or virtual network software.

Troubleshoot import and update problems

If a subscription fails to add or refresh, use the error message and the point of failure to narrow down the cause. Repeatedly pasting the same URL usually does not help, and deleting the entire application data directory can remove working profiles and preferences. Start with the checks below, then retry once after correcting the likely issue.

Invalid URL or request error: Check that the entire URL was copied, begins with the expected scheme, and has no extra spaces or quotation marks. Some providers issue a new URL after a subscription reset.
Timeout or connection refused: Check whether the device can reach the subscription domain on the current network. A provider outage, DNS problem, firewall, or temporary network restriction can prevent the download. Compare with another network only if it is safe and permitted.
HTTP 401 or 403: The server may require a valid token or may reject the request because of an account, address, or access policy. Check the provider’s dashboard and ask its support team about the exact response code.
HTTP 404: The URL may have expired, been copied incorrectly, or been replaced by the provider. Confirm the current subscription link instead of guessing or modifying its path.
Download succeeds but configuration parsing fails: The response may not be a Clash-compatible configuration, may be an HTML login or error page, or may contain fields unsupported by the active core. Confirm the provider’s format and inspect the client’s parsing message.
Profile imports but no usable nodes appear: Check whether the provider’s configuration uses policy groups or remote rule providers, and look for errors in the client log. A blank-looking node page does not always mean the subscription URL returned no configuration.
Refresh completes but nothing seems different: The provider may not have changed the configuration, or the active profile may not be the one you refreshed. Check the profile name and update time before importing the URL again.

If the problem persists, note the Clash Verge Rev version, operating system, active core name and version, approximate time of the failed request, and the exact non-sensitive error text. Do not include the subscription URL, authorization headers, node passwords, or unredacted logs in a public report. If you contact the provider, ask whether the URL is valid, whether the response format is compatible with Clash Verge Rev, and whether the server returned a specific HTTP status.

When the profile updates successfully but traffic still does not work, return to the layers in order: confirm the intended profile is active, select a node or policy group, check the client’s operating mode, and verify that System Proxy is enabled. Then inspect the connection list for the affected application. This makes it easier to tell a subscription-download problem from a node reachability issue or an application that is bypassing the system proxy.