Clash Verge Rev Subscription Setup: Add Profiles and Pick Nodes
Before adding a subscription
Clash Verge Rev is a desktop client that manages a proxy core, configuration profiles, and operating-system proxy settings through a graphical interface. A subscription is not the same thing as a single proxy node. It is usually a URL provided by a proxy service that returns a configuration containing nodes, proxy groups, rules, and other settings. After importing that configuration, the client can show the available profiles and let you choose a node or a policy group.
Before you start, obtain a subscription URL from the service that issued your account. It may be shown as “subscription,” “Clash,” “Mihomo,” or “configuration” in that service’s dashboard. Copy the complete URL, including its protocol and any query string. Do not remove characters after a question mark, add spaces, or substitute the client’s profile name for the URL. A profile name is only a local label; the subscription URL is what the client uses to retrieve configuration data.
Check that the service provides a format compatible with the core selected in Clash Verge Rev. Many current subscriptions are designed for Mihomo, while some providers offer a separate Clash-compatible link. If the provider has a format selector, choose the format recommended for Mihomo or Clash Verge Rev rather than copying a link intended for a different client. A link that downloads HTML, a login page, or an incompatible configuration will not become usable just because it has been added to the client.
Keep the subscription URL private. Anyone who can use an active URL may be able to retrieve your configuration or consume account traffic, depending on the provider. Avoid pasting it into public chat, screenshots, issue reports, or online configuration validators. If the URL is exposed, revoke or regenerate it in the provider’s dashboard when possible.
Add the subscription profile in Clash Verge Rev
Open Clash Verge Rev and let the application finish starting before adding a profile. The wording and placement of controls can differ slightly between releases, and some builds reorganize the navigation. Look for the Profiles page or a profile-management button, then choose the option to add a remote profile or paste a subscription URL. If the interface offers several import types, select the remote URL option rather than importing a local YAML file.
Paste the complete subscription URL into the address field. If the dialog also asks for a name, enter a short label that will help you recognize the profile, such as the provider name or account type. The label is for display only and does not change the subscription contents. Avoid putting your full subscription URL in the name field, because that can make it harder to manage the profile and may expose sensitive information on screen.
Where available, leave the update interval at the provider’s recommended value. An interval controls how often the client requests a newer copy of the configuration; it does not necessarily control how often individual node details change. A very short interval can create unnecessary requests, trigger provider-side limits, or make troubleshooting more confusing. You can also update a profile manually when you need to check for recent nodes or configuration changes.
Submit the dialog and wait for the import to finish. A successful import normally creates a profile entry and displays configuration or provider information. Select that profile to make it the active configuration. Some versions activate it automatically after a successful import; other versions require you to click the profile entry or use a separate activation control. Confirm which profile is marked active before testing traffic, especially if you already have local or remote profiles in the list.
If you have a local YAML configuration with custom rules or overrides, do not assume that adding a subscription merges it automatically. A remote profile may be refreshed from the provider, and edits made directly to downloaded content can be replaced on the next update. Use the client’s supported merge or override features only if you understand how the configuration is combined. For a first setup, use the subscription as provided and verify that it works before adding custom changes.
Refresh the profile and start proxying
Once the profile appears in the list, refresh it if the client has not already downloaded its contents. On the Profiles page, use the refresh or update control associated with that profile; depending on the build, this may appear as a button, an icon, or an action in a menu. Wait for the operation to complete instead of clicking repeatedly. A successful refresh should update the profile’s timestamp or status and make its available groups and nodes accessible to the client.
Next, confirm that the selected profile is active, then start the core if it is not already running. Clash Verge Rev separates configuration selection from traffic control: an imported profile can exist without being active, and an active profile can be loaded while proxying remains disabled. Check the main dashboard or status area for a running indicator and inspect the core log if the application reports a startup error.
For ordinary desktop use, enable the client’s System Proxy control to route applications that follow the operating system’s proxy settings. This is usually the simplest way to test a browser or other proxy-aware application. System Proxy does not force every program to use the proxy. Some command-line tools, games, and applications have their own network settings or connect directly, so a working browser alone does not prove that every application is using Clash Verge Rev.
TUN mode is a separate option that can capture a broader range of traffic by creating a virtual network interface. It may require administrator permission, a system service, or confirmation from the operating system. Do not enable TUN just to solve an ordinary profile-import issue. First verify that the profile loads, the core runs, a node can connect, and System Proxy works. If you later need TUN, enable it using the client’s supported controls and check the relevant permission prompts and logs.
Check the client’s proxy mode before testing. In Rule mode, the configuration’s rules decide whether traffic goes to a proxy group, connects directly, or is handled another way. In Global mode, traffic that reaches the proxy is generally sent through the selected global proxy group. These modes change how rules are applied; neither mode can repair an invalid profile or a failed node connection. For routine use, follow the configuration and provider’s guidance, and use Global mode only as a temporary diagnostic if you need to distinguish a routing-rule issue from a connectivity issue.
Choose a node and verify the connection
Open the proxy-group or node-selection view after the profile has loaded. Subscription configurations often organize nodes under groups with names such as “Select,” “Auto,” “Fallback,” or a provider-specific label. A group is a policy that can contain multiple nodes or even other groups. The group name you see on the dashboard may therefore not be a server itself; selecting a node inside the group is a separate action.
For a straightforward first test, open the primary selection group and choose a node that is available and clearly identified. If the client provides a latency-test control, run it after the group has loaded. A test result can help compare response times to the test destination, but it is not a complete measure of speed, stability, or access to every website. A node with the lowest displayed delay may be congested, may have a poor route to the service you need, or may not support the destination’s protocol requirements.
If the configuration offers an automatic selection group, it may choose among its members according to the group’s configured behavior and health checks. A manual selection group lets you choose a specific member yourself. A fallback group may use another member when its preferred one is unavailable. These behaviors are defined by the configuration, so do not assume that every group named “Auto” works in exactly the same way. If an option is missing, the subscription may not include that group, the profile may have failed to parse, or the interface may need to finish loading.
After choosing a node, open a new browser tab or make a fresh request to a site that should use the proxy. Check the connection list or activity view in Clash Verge Rev and confirm that the new request appears with an appropriate rule and proxy group. Existing browser connections can remain open after you change nodes, so reload the page or open a new connection before judging the result. If you are testing a command-line application, remember that it may ignore System Proxy; configure its proxy support separately or test with an application known to follow the operating-system setting.
When the connection works, you can compare a few nodes rather than repeatedly cycling through the entire list. Record the node or group that works reliably for your usual destination, and keep the configuration’s original rules unless you have a specific reason to change them. If the provider updates its subscription, new nodes may appear, old ones may be removed, and group membership may change. A previously selected node can consequently disappear or become unavailable after a refresh.
Troubleshoot import errors and missing nodes
If the URL is rejected during import, first verify that the copied address is complete and current. Re-copy it from the provider’s dashboard rather than manually retyping it. Check whether the provider requires an account login, whether the subscription has expired, and whether the service displays a usage or access restriction. You can test whether the address is reachable by opening it privately in a browser, but do not share the resulting configuration or URL. A browser download that contains an error page, a sign-in prompt, or plain text unrelated to a proxy configuration indicates that the client is not receiving a usable subscription document.
If the import fails with a parsing or configuration error, note the exact message and inspect the core log for the first relevant error. Common causes include a provider returning an unexpected format, invalid YAML indentation, an unsupported field for the selected core, or a temporary incomplete response. If the provider offers a separate Mihomo or Clash format, try the format recommended for the installed core. Do not solve a parser error by deleting random sections from the subscription; rules, groups, and proxy names can reference one another, and removing one part may create additional errors.
If the profile imports but no nodes are visible, refresh the profile once and wait for the result. Then confirm that the correct profile is active and check whether the configuration organizes nodes inside a group rather than listing them as a flat set. If the group view is empty, inspect the profile status and core log. The provider may have returned a configuration with no available nodes, the account may have reached a limit, or the configuration may contain an error that prevents parts from loading. Contact the provider with the time of the failed update and the non-sensitive error text; never send a subscription URL or account token in a public support request.
If nodes are visible but latency tests fail, distinguish a test failure from a complete proxy failure. The test URL may be blocked, unreachable, or unsuitable for the node type. Try another provided node and make a fresh request to a normal destination, then check the connection log. If every node fails, verify that the core is running, the device has an internet connection, the system clock is correct, and no firewall or security application is blocking the client. If only one node fails, the issue may be limited to that server or route; choose a different available node and report the affected entry to the service provider.
If the selected node looks correct but applications still connect directly, check whether System Proxy is enabled and whether the application follows the operating-system proxy. In Rule mode, review the matched rule and the group shown for the connection. A rule may intentionally route a domain through DIRECT, or a domain may match a different group than expected. To troubleshoot without changing the configuration permanently, compare a fresh request under the provider’s recommended mode, then restore the original mode and review the relevant rule before making edits.
Finally, check for local conflicts. Another proxy client may already be using the same listening port or controlling the system proxy. Close other proxy applications, restart Clash Verge Rev, and review its startup log for port-binding or permission errors. If the profile previously worked and stops after an update, compare the update timestamp and error details, then retry once after confirming that the provider service is available. Keep the original URL private, preserve a copy of any custom configuration that is yours to edit, and make one change at a time so that the next test has a clear result.