1. Scope, prerequisites, and subscription basics
This guide is for people who already have Clash Verge Rev installed and have received a subscription URL from a provider they are authorized to use. It covers adding that remote profile, loading it, choosing a proxy, and refreshing the node list when the provider changes it. The exact labels and button positions can differ between Clash Verge Rev releases, but the underlying workflow is the same: add a remote profile, let Mihomo fetch and parse its configuration, then select a proxy from the loaded profile.
An airport subscription is usually a private URL that returns a Clash-compatible configuration or a provider-specific response that the client can convert into one. It is not necessarily a single server address. The response may contain many proxy nodes, groups, routing rules, and update metadata. That is why you normally add the URL as a remote subscription rather than pasting it into the manual YAML editor or entering it as a proxy node.
Before starting, check that Clash Verge Rev is installed from a source you trust, that your computer can access the provider’s service, and that the URL has been copied in full. Some links are long and contain characters such as ?, &, or =; a missing character can make the request fail. Do not post the URL in a screenshot, issue report, public chat, or browser address bar shared on a screen recording. Anyone who obtains an active subscription link may be able to use the account or consume its traffic.
A subscription URL is a credential, not a harmless bookmark. Treat it like a password: use the provider’s account page to revoke or regenerate it if it is exposed, and avoid saving it in shared documents or shell history. This guide cannot verify a provider’s safety or availability. Follow the provider’s terms and any workplace network policy, and do not import a configuration from an unknown source just because it promises free nodes.
2. Add the subscription as a remote profile
Open Clash Verge Rev and go to the area labeled Profiles or Config, depending on the version. Look for an action to add a profile, import a remote configuration, or add a subscription. Choose the remote or URL-based option. Avoid selecting a local file import unless the provider gave you a downloaded YAML file; the two methods represent different update workflows.
Copy the complete subscription URL from the provider’s official account page. If the provider offers several formats, choose the option explicitly marked for Clash, Mihomo, or Clash-compatible clients.
Paste the URL into the subscription address field. If the dialog also asks for a profile name, use a neutral label such as the provider name or “Personal subscription.” A descriptive name helps distinguish profiles later, but do not include account credentials in it.
Confirm the import or add action. The client should make a network request, retrieve the remote content, and display the new profile in the profile list.
If the dialog offers an update interval, choose a reasonable value or leave the provider’s recommended default. Very frequent polling rarely makes a node list fresher and can trigger rate limits.
After the request completes, inspect the new profile’s status and update time. A profile appearing in the list does not always mean it has loaded successfully: some versions show the entry even when fetching or parsing failed. Look for an error indicator, a last-updated timestamp, or a notification. If the client reports that the format is invalid, verify that you selected a Clash-compatible subscription, rather than a generic URL intended for another application.
Do not paste a subscription address into the browser to “test” it on a shared or managed computer. Browsers may retain URLs in history, sync them to an account, or expose them to extensions. If you need to check the provider response, use the client’s own update action and inspect only the error message or status. Never share the full URL when asking for support; redact the path and query string, or replace the sensitive portion with a placeholder.
3. Load the profile and choose a proxy
Once the remote profile has downloaded, activate it using the profile’s select, use, or switch control. Some versions activate a profile as soon as it is imported; others require a separate click. Check which profile is marked current before changing settings, especially if you also keep a local configuration or another provider’s subscription. Selecting the wrong profile can make it appear that the subscription contains no nodes even though the imported profile is valid.
Next, open the Proxies or proxy-group view. A provider’s configuration often organizes nodes into groups such as “Proxy,” “Auto,” “Global,” or regional groups. These group names and their behavior come from the provider’s configuration, so they will not be identical for every subscription. Click a group and select a node, or select an automatic group if the provider supplies one. A selected group may itself point to another group; follow the available choices until an actual node or automatic strategy is selected.
For a first connectivity check, choose a node with a nearby region and a clear status rather than assuming that the first item is the best. If the client exposes a delay test, run it after the profile is active. A latency result is only a short network measurement: it does not guarantee that every website or application will work, and a low number does not necessarily mean the route is stable under load.
Check the system proxy or TUN status only if your goal is to route applications through the client. Importing a subscription and selecting a node are separate from enabling system-level traffic capture. Browser testing may work through a system proxy while a command-line program does not, or the reverse, depending on the operating system and application. Start with one test application and one destination; avoid changing DNS, TUN, routing rules, and proxy mode at the same time, because that makes a simple import problem harder to isolate.
If the profile contains policy groups, a node selection may not affect every connection. Rules can direct different destinations to different groups or to DIRECT. That is normal for a rule-based configuration. When checking whether a selected node is being used, consult the client’s connection or log view and inspect the rule and outbound shown for a test connection. Do not infer the route solely from the name displayed in the proxy list.
4. Refresh the subscription and understand what changes
To refresh the node list, return to the profile page and use the profile’s update, refresh, or reload action. Wait for the request to finish before clicking again. A successful refresh retrieves the provider’s latest response; depending on the provider, that response may add nodes, remove expired nodes, change groups, revise rules, or leave the configuration unchanged. A refresh does not necessarily reset the currently selected proxy, so verify the selection afterward if a connection behaves differently.
Automatic update intervals can be useful when a provider rotates endpoints, but they are not a substitute for understanding the provider’s renewal policy. If a subscription has expired, refreshing it will not restore access unless the account is renewed or the provider resolves the entitlement. Conversely, if the list is stable and the provider does not require frequent updates, manual refresh may be sufficient. Avoid repeatedly polling during a provider outage; it can create unnecessary load and may cause temporary rate limiting.
Use this quick comparison to distinguish common profile actions:
| Action | What it does | What it does not do |
|---|---|---|
| Add URL | Creates a remote profile entry in the client | Does not prove that its content parsed correctly |
| Update profile | Fetches the latest remote configuration | Does not renew an expired provider account |
| Select profile | Makes that configuration the active profile | Does not automatically guarantee system-wide traffic capture |
| Select proxy | Chooses an outbound or policy group within the active profile | Does not override every rule in the configuration |
If you edit a remote profile locally, remember that a later update may overwrite parts of your changes. Keep customizations in a supported override or merge mechanism if your client and configuration provide one, and save a backup before making changes. Do not assume that editing the displayed YAML changes the provider’s source; it changes only the copy managed by your client, and an update may replace that copy with the server response.
5. Troubleshoot missing nodes and failed updates
When no nodes appear, first confirm that the imported profile is selected and that the client finished parsing it. Then check the profile’s last update result and open the log or notification details. A blank proxy page can mean an empty provider response, an incompatible format, a failed conversion, or simply that the wrong profile is active. These cases look similar in the interface but require different fixes, so use the reported error instead of repeatedly reimporting the same URL.
Timeout, connection refused, or DNS error: Confirm that the computer has a working connection and that the provider’s service is reachable from the current network. Check the system clock and try the update once more after a short pause. If other sites work but the provider endpoint does not, ask the provider whether its subscription service is operational.
Unauthorized, forbidden, or expired response: Sign in to the provider’s official account page and check the subscription status, device limit, and renewal date. Do not try to “fix” an entitlement error by editing the URL. If the provider offers a regenerate-link option, use it only from the official account interface.
Invalid YAML or unsupported format: Confirm that the URL is for a Clash- or Mihomo-compatible client. Some services offer separate links for different applications, and a response designed for another client may not parse in Clash Verge Rev. If the provider recently changed its output format, request a compatible link or current setup instructions.
Update succeeds but the list is still empty: Check whether the provider’s response contains nodes or only references another format. Verify that a filter, conversion option, or profile override has not excluded every proxy. If you can inspect the response safely, do so without copying the secret URL or configuration into a public support channel.
Nodes appear but tests fail: Try another node or group, check the client’s connection log, and verify that system proxy or TUN is enabled only if required for the test application. A subscription can load correctly while a particular server is offline, overloaded, or unreachable from your network.
For a useful support report, note the Clash Verge Rev version, operating system, approximate update time, profile status, and the exact non-sensitive error text. Include whether other profiles update successfully and whether the problem affects all nodes or only one group. Remove the subscription URL, authentication tokens, user identifiers, and any private configuration values from screenshots and logs. If a link has already been exposed, revoke or regenerate it first rather than relying on a promise that it will not be reused.
6. Keep the subscription private and the setup maintainable
Remote profiles are convenient because the provider can publish changes in one place, but that convenience creates a trust relationship. The imported configuration can define proxies, groups, DNS behavior, and routing rules. Review the source and provider documentation, keep the client updated from a trusted distribution channel, and be cautious about configurations that request unexpected permissions or direct traffic in ways you do not understand. A subscription link does not make the provider’s infrastructure private or guarantee the confidentiality of traffic passing through it.
If you manage more than one profile, name each one clearly and record which account or device it belongs to without storing its secret URL in the name. Remove profiles you no longer use, but first check whether local overrides or settings depend on them. Keep a separate note of the provider’s official renewal and recovery process. If a profile stops working after an update, note the time and error before rolling back or replacing it; that information helps distinguish a client regression from an expired account or a provider-side outage.
When troubleshooting, change one variable at a time. Update the profile, confirm that it loaded, select a node, then test a single application. Only after that should you investigate system proxy, TUN mode, DNS, or routing behavior. This sequence keeps the diagnosis grounded: if the subscription request failed, changing TUN settings will not repair it; if the nodes loaded but a rule sends a destination to DIRECT, repeatedly refreshing the URL may not change that route.
Some single-purpose VPN apps make initial setup feel simpler, but they may offer fewer ways to inspect profile updates, choose policy groups, or diagnose a specific route. Clash Verge Rev exposes those controls, so you can distinguish a failed subscription fetch from a node outage or a rule-selection issue instead of treating every problem as a single on/off switch. If you want to compare supported clients for your operating system and continue with a setup guide, start with the official download and tutorial pages.
Ready to get started?
Choose a client for your platform, then follow the setup guide to add and manage your profile.