Clash Verge Rev Subscription Setup: How to Add a Profile

1. Understand What a Subscription Profile Contains

In Clash Verge Rev, a subscription profile is a remote configuration that the client can download and use. The profile usually contains proxy server details, proxy groups, routing rules, and sometimes DNS or other core settings. Adding the profile gives the client a source to fetch; it does not necessarily activate that configuration or prove that its nodes are reachable.

It helps to separate three parts of the process. The subscription URL is the address used to retrieve configuration data. The profile is the saved entry in Clash Verge Rev that remembers that address and its update options. The active configuration is the one currently loaded by the core. A profile can appear in the list while another profile remains active, and a downloaded configuration can still fail to load if it is invalid or incompatible with the selected core.

Providers may supply a full Clash-compatible YAML configuration, a URL that returns a configuration after authentication, or a service-specific link intended for a particular client. Some providers also offer a conversion page or separate links for different core formats. Use the subscription URL that the provider identifies for Clash or mihomo, rather than copying a dashboard address, a single proxy-server address, or a link intended for another application.

• Subscription URL: A remote address, often containing a private token, from which the client retrieves configuration data.
• Profile: The saved subscription entry, which can usually be updated without pasting the URL again.
• Active configuration: The configuration currently selected for the core to parse and use.
• Proxy group: A selector or policy in the configuration that determines which proxy or route a connection uses.

Clash Verge Rev is the graphical client; its core is responsible for parsing the configuration and making connections. Many current configurations rely on mihomo-specific protocols or fields, but support depends on the core version actually selected in the client. The interface version and the core version are separate. If a profile imports but reports an unsupported proxy type or unknown configuration field, check the active core and the provider’s compatibility notes before changing unrelated settings.

2. Prepare the URL and Check the Client

Before importing, confirm that Clash Verge Rev is installed from a source you trust and launches normally. Menu labels and layout can differ between releases, operating systems, and language settings, so the steps below refer to the general profile workflow rather than promising an identical button name in every build. In the application, look for the profiles or configuration area, commonly shown as Profiles in the sidebar.

Copy the complete subscription URL from your provider’s account or subscription page. If the provider offers several formats, choose the Clash, Clash.Meta, or mihomo-compatible option according to its instructions and the core available in your client. A browser address that opens the provider’s dashboard is not necessarily a subscription URL. Avoid removing query parameters or editing the token: a link that looks long or includes symbols may be complete as provided.

• Check that the link begins with the expected scheme, usually https://, and that the entire address was copied.
• Confirm that the subscription is enabled and has not expired or reached a device or traffic limit.
• If the provider supplies a dedicated Clash Verge Rev import method, follow its instructions; otherwise, use the remote-profile option in the client.
• Do not paste the subscription URL into a node’s server, port, or password field. Those fields describe an individual proxy, not a remote configuration.

A subscription URL is not the same thing as a profile’s local name. The name is a label used to identify the entry in the client; it can usually be something recognizable, such as the provider name or account. Avoid putting the complete URL in the name, because the label may be visible in screenshots or logs.

If you have used another proxy client, close it while testing the first import. Two clients may try to change the system proxy or use the same local ports. That conflict does not usually prevent a profile from being downloaded, but it can make later connectivity checks confusing. For the initial test, keep the setup simple: one client, one profile, and no extra TUN or routing changes unless they are required.

3. Add the Subscription and Activate It

Use this sequence for a first import. The exact wording may vary by Clash Verge Rev version, but the key steps are to create a remote profile, supply its URL, update it, and then select it as the active configuration.

1. Open the profile list. In Clash Verge Rev, select the profiles or configuration section. Review the list first so you do not accidentally replace a profile that is already working.
2. Create a remote profile. Choose the add or new-profile action and select the option for a URL, remote configuration, or subscription. Do not choose a local-file import unless you have a YAML file saved on your device.
3. Enter the details. Paste the full subscription URL into the URL field. Add a short, recognizable name if the interface provides one. Check the pasted address from beginning to end, especially if it was copied from a page that wrapped the text across lines.
4. Save the profile. Confirm the add or save action. The profile should appear in the list. If the interface starts downloading automatically, allow that request to finish before clicking repeatedly or creating a duplicate entry.
5. Update the profile. Use the profile’s update or refresh action if the first download did not run automatically. Wait for the result. A profile name appearing in the list only confirms that an entry was saved; it does not confirm a successful download.
6. Make it active. Select the newly imported profile using the client’s activate, use, or selection control. Look for the active indicator, then give the core time to reload the configuration. Do not assume that adding a profile switched away from the previous one.
7. Check the proxy groups. Open the proxy or group view and confirm that expected groups and nodes are present. Select a usable node or policy if the configuration does not choose one automatically.

After activation, check the client’s connection or log view for a configuration-load result. A successful update means the client received data; a successful load means the core accepted the configuration. These are separate checks. If the core reports a parsing error, note the exact message and the profile being loaded rather than repeatedly refreshing without identifying the cause.

4. Refresh the Profile and Confirm It Is Usable

To refresh an existing subscription, select its entry and use the update or refresh action associated with that profile. The client requests the current configuration again using the saved URL. In normal use, this is preferable to deleting the entry and adding it again: refreshing preserves the profile identity and may retain its update settings. If the provider changes the URL or token, edit the saved address using the profile’s edit control, then run an update.

After the request finishes, verify the result in more than one place. A useful first check is whether the profile shows an updated time or a successful update status. Next, confirm that it remains the active profile. Then open the proxy groups and inspect whether nodes are listed. Finally, select a node or group appropriate for your setup and test a new connection. A page that was already open may reuse an old connection, so start a fresh request when comparing results.

A successful node delay test is useful, but it is not a guarantee that every application will use that node. In rule mode, the matching rule may select a different group or DIRECT. The system proxy generally covers applications that honor the operating system’s proxy setting; TUN captures traffic through a virtual network interface and has separate permission and routing requirements. First verify the subscription and group selection, then investigate system proxy or TUN coverage if only particular apps bypass the proxy.

Updates can replace the remote configuration content. Avoid editing generated subscription files directly unless you understand how the client stores them and how updates are merged. A direct edit may disappear on the next refresh. If you need custom rules or local changes, use the override, merge, or script features supported by your client and core, and keep a backup before changing them.

5. Troubleshoot Import Errors and Empty Node Lists

When an import fails, identify which stage failed: saving the URL, downloading its response, parsing the response, activating the configuration, or establishing a connection. The same “not working” symptom can come from different causes. Check the client’s update status and core log for a specific error before changing settings or reinstalling the application.

• Unauthorized or forbidden response: An HTTP 401 or 403 commonly points to an expired, incomplete, or unauthorized link, or to provider-side access restrictions. Sign in to the provider’s official page and copy a fresh URL. Check account status, traffic limits, and device limits.
• Not found: An HTTP 404 may mean the address is incomplete, the subscription endpoint has changed, or the link has expired. Copy the current URL rather than trying to guess or manually reconstruct its path.
• HTML instead of configuration: A login page, account notice, or ordinary web page is not a usable Clash configuration. The browser may display it successfully while the client cannot parse it. Use the provider’s actual subscription link and check whether authentication or a required format option is missing.
• Timeout or connection error: Check the device’s internet connection, DNS availability, firewall or security software, and the provider’s service status. If the URL works only in a browser, verify whether the browser is signed in or adding authentication that the client does not have.
• Parsing or unsupported-type error: The configuration may use malformed YAML, fields unsupported by the active core, or a proxy protocol that the core version does not implement. Record the exact error, identify the selected core, and ask the provider which core format the subscription requires.
• Update succeeds but no nodes appear: Confirm that the intended profile is active and that the provider has issued a node-bearing configuration. Some subscriptions contain only rules, groups, or policy references, and some providers require choosing a format or region on their dashboard.

For an empty node list, also inspect the configuration’s proxy groups. A group can exist without directly displaying every node, and a provider may use nested groups or filters. If the client shows groups but no selectable proxies, the received configuration may be incomplete, filtered, or designed for a different core. Do not paste your full subscription URL into a public YAML validator to investigate it; the token may be exposed to the service operator.

If the profile is active and nodes are listed but a test still fails, confirm that the node details have not expired and that the device can reach the provider’s proxy servers. Check whether another VPN or proxy client is interfering. Review the core log for DNS failures, connection timeouts, or protocol errors. When asking the provider for help, share the client and core versions, operating system, sanitized error text, and update time—but remove subscription URLs, tokens, passwords, server addresses, and other account-specific information.

A reliable routine is straightforward: keep the provider’s subscription link private, refresh the existing profile when needed, verify that the response parsed, make the intended profile active, and then test a node and a real application separately. This sequence distinguishes a profile-import problem from a routing or traffic-capture problem and makes future updates easier to diagnose.