1. Understand what you are importing
An airport subscription is a remote URL issued by a proxy service. In Clash Verge Rev, adding that URL as a remote profile lets the application retrieve a configuration and display the proxy nodes it contains. The URL is not the same thing as a node address: it may point to a complete YAML configuration, a provider-managed list, or a service endpoint that generates a compatible profile for your account. The exact format depends on the provider and the options associated with your subscription.
This guide covers the common workflow: obtain the subscription URL from your provider, add it to Clash Verge Rev, wait for the profile to download, and check that the expected proxies and groups appear. It also explains what to inspect if the import fails or the profile loads without the nodes you expected. Interface labels can vary slightly between releases, so look for the profile or configuration area rather than relying on one particular button name.
A subscription URL often contains a long token in its path or query string. Anyone who obtains a usable URL may be able to retrieve your profile, use the associated service, or consume part of your account allowance. Treat it like a password: do not paste it into a public issue, screenshot it for a forum post, or send it to someone who is only helping with a general setup question. If it has been exposed, use the provider’s account controls to revoke or regenerate it.
Before importing, check that the provider explicitly supports Clash, Mihomo, or a compatible profile format. Some services offer separate links for different clients, and a link intended for another application may return a format that Clash Verge Rev cannot parse. If the provider offers a client selector, choose the Clash-compatible option, and note whether it lets you select a format such as YAML. Keep the provider’s own instructions nearby; they are the authority for account status, link generation, and service limits.
It is also useful to distinguish a remote profile from a locally managed configuration. A remote profile is fetched from its source and may be refreshed later to obtain updated nodes, groups, or rules. A local file is edited or maintained on your device. If you import a remote subscription and then make direct changes to its downloaded contents, a later refresh may replace those changes. When you need custom rules, check whether the application or your provider supports overrides, scripts, or a separate local configuration workflow instead of assuming edits to the remote profile will persist.
2. Prepare the URL and check the profile
Start by signing in to the provider’s official account page. Find the subscription, client configuration, or connection details section, and copy the URL from there. Avoid copying a browser address bar from a page that merely displays subscription details; the address of the account page is not necessarily the subscription endpoint. If the provider supplies multiple links, identify which one is intended for Clash or Mihomo and whether it requires a conversion option or client identifier.
A valid subscription URL usually begins with https://, although a provider may document a different scheme or an additional authentication step. Do not remove query parameters, shorten the URL, or edit its token to make it look tidier. Those characters can be part of the provider’s access mechanism. When copying on a desktop, use the provider’s copy button if available, then paste into a private text field only to check that the beginning and end of the value are present. Do not include the full URL in a screenshot or diagnostic report.
Before importing, check a few basics. Confirm that your subscription has not expired, that the provider has not paused the account, and that your device has a working internet connection. If the provider has a data or device limit, verify that you have not reached it. A profile request can fail even when the desktop application is working normally: the server may reject an expired token, apply an account restriction, or return a temporary error. Knowing the account state first makes it easier to separate a provider-side problem from an application-side one.
Make sure you are using a current, trusted build of Clash Verge Rev obtained from its official distribution channel. The application name alone does not guarantee that every fork, repack, or old release behaves the same way. If you are troubleshooting an existing installation, record the application version and operating system before changing anything. That information is useful when comparing menus or reporting a reproducible problem, but it does not require you to share the private subscription URL.
The first successful import may download a profile but not automatically select a proxy for every connection. Importing, refreshing, selecting a proxy group, and enabling the system proxy are separate actions. Treat them as separate checks. This distinction prevents a common misdiagnosis: seeing the profile in the application proves that it was added, but does not by itself prove that the intended node is selected or that applications are using the proxy.
3. Add the subscription and verify the result
The following sequence is a practical starting point. The exact control names may differ across Clash Verge Rev releases, but the steps remain the same: open the profile manager, add a remote profile, provide the URL, allow the download to complete, and inspect what the application received.
- Open Profiles. Launch Clash Verge Rev and locate the page or panel that lists profiles or configurations. If an existing profile is active, note its name before adding another one so you can tell the new entry apart.
- Add a remote profile. Use the add, import, or remote-profile control. Choose the option for a URL or remote configuration rather than selecting a local file. If the application offers a subscription-specific option, use it when that matches the provider’s instructions.
- Enter the subscription URL. Paste the complete URL into the relevant field. Give the profile a recognizable local name if the interface allows it, such as the provider name plus a short date or purpose. A descriptive name helps when you later have several profiles; it does not change the private URL or the provider’s settings.
- Save and fetch the profile. Confirm the import and wait for the application to finish its request. Do not repeatedly click the add button while a download is still in progress, because that can create duplicate entries and make later checks confusing.
- Select the imported profile. If the profile list shows a success state, select or activate the new entry according to the application’s interface. Some versions select it automatically; others leave it available without switching the active configuration.
- Inspect the proxies and groups. Open the proxy or group view and check whether the expected nodes and provider-defined groups are present. A profile can load successfully yet contain no usable nodes if the provider response is empty, filtered, or not in the format you expected.
- Test one destination. Choose an available proxy group or node, then use the application’s connection test if provided. Test a destination you are permitted to access and compare the result with the application’s connection state. A test of one node is not a guarantee that every rule, application, or destination will use that node.
After the profile is active, check the application’s proxy mode and system-proxy controls only if your goal is to route device traffic through Clash Verge Rev. These settings affect how traffic is handled; they are not part of the subscription import itself. A rule-based profile may send different destinations through different groups or directly to the network. If a browser behaves differently from another application, inspect the selected profile, mode, and relevant rules before assuming that the subscription is broken.
For a clean verification, record the profile name, the time of the first successful update, and whether the expected groups appeared. Avoid recording the full URL or exporting a configuration that includes credentials. If you later need support, a redacted error message, application version, operating system, and a description of the step that failed are usually more useful—and much safer—than a screenshot containing the subscription token.
4. Refresh profiles without losing track of changes
Providers can update remote profiles to add, remove, or reorganize nodes. To fetch those changes, return to the profile list and use the refresh or update control for the relevant entry. Wait for the request to finish, then revisit the proxy and group views. If you have more than one profile, confirm that you refreshed the intended one; updating a different entry can make it appear as though the subscription did not change.
A refresh retrieves what the provider currently serves. It does not necessarily renew an expired account, change your plan, or repair an invalid URL. If the update fails, note the displayed error and check your account status at the provider. If the profile refreshes successfully but looks unchanged, the provider may not have made a change, or its service may update on a schedule. Ask the provider about its refresh behavior rather than repeatedly deleting and re-adding the profile.
Be cautious about editing a provider-managed profile directly. Some clients keep remote profiles in an application-managed location, and refreshing may overwrite local edits. If you need custom routing, first check the provider’s documented options and the features available in your Clash Verge Rev version. Keep a backup of any configuration you are entitled to manage, and make changes through a supported override mechanism where available. Do not assume that a downloaded copy is the same as the authoritative remote profile.
Subscription URLs should stay private after setup. Avoid placing them in shell history, public repositories, shared notes, chat transcripts, or screenshots. If you must transfer the URL between your own devices, use a private channel and remove any temporary copy when you are done. When submitting a bug report, redact the token, query string, and any username or account identifier. A useful redaction preserves the URL’s general shape—for example, the scheme and a provider hostname—without revealing the access value.
If you no longer use a subscription, remove its profile from the application and consider revoking the URL through the provider’s account page. Removing a local entry does not always invalidate a link that has already been copied elsewhere. Revocation is especially important if the URL was sent to the wrong person, included in a public screenshot, or stored in a repository that was accessible to others. Treat exposure as a credential incident, not just as a display mistake.
5. Diagnose failed imports and missing nodes
When an import fails, begin with the simplest checks and change one thing at a time. Confirm the URL was copied in full, that the device can reach the provider, and that the account is active. Then retry a single refresh and read the complete error shown by the application. A timeout suggests a different problem from an HTTP rejection or a YAML parsing error, so the wording and timing of the failure can narrow the investigation.
| Symptom | Likely areas to check | Practical next step |
|---|---|---|
| Request times out or cannot connect | Network access, provider availability, DNS, or a temporary outage | Check the provider status and retry once on a known working connection. |
| Unauthorized, forbidden, or expired response | Revoked, expired, incomplete, or account-restricted subscription URL | Generate or copy a current link from the provider account page. |
| Profile downloads but cannot be parsed | Unsupported format, an HTML error page returned instead of a profile, or an incompatible client option | Choose the provider’s Clash/Mihomo format and follow its conversion instructions. |
| Profile loads but has no nodes | Empty provider response, account limits, filters, or a provider-side configuration issue | Check account status and ask the provider whether the subscription currently contains nodes. |
| Nodes appear, but connection tests fail | Unavailable nodes, a selected group with no usable choice, or a network path problem | Try another listed node and inspect the application’s connection log. |
If the application reports an unsupported format, do not try random converters or paste the private URL into an unfamiliar website. First verify that the provider generated a link for Clash or Mihomo and that the response is meant to be a client profile rather than a webpage or a list for another protocol. A service may support multiple output formats, and choosing the wrong one can produce a response that looks like a failed import even though the URL itself is reachable. Ask the provider for its current Clash Verge Rev instructions if the format selector is unclear.
Missing nodes deserve a separate check from import errors. A profile can be valid YAML and still contain no proxies because an account has no active allocation, a service is temporarily empty, or provider-side filters exclude the available entries. Compare the result with the provider’s account dashboard or documented node list. If the provider confirms that nodes should be present, send support the time of the refresh, the client version, and a redacted error or response summary. Never send the unredacted subscription link unless the provider explicitly requests it through a trusted private support channel.
When nodes are present but a connection test fails, test more than one node if the provider offers alternatives. Check that the intended proxy group is selected and that the profile is active. Then use Clash Verge Rev’s logs to identify whether the failure occurs during DNS lookup, connection establishment, or the test request itself. A node can be listed but temporarily unavailable, while a successful profile download only confirms that the configuration endpoint responded; it does not prove that every relay is reachable.
If the same link works on another device but not this one, compare application versions, system time, network restrictions, and any security software that might block the request. If the link fails everywhere, contact the provider before repeatedly changing local settings. Avoid deleting a working profile until you have confirmed that you can retrieve the URL again. Keeping the original entry until the replacement succeeds can prevent an avoidable interruption.
Compared with basic VPN clients that offer only a single on/off switch, a Clash-compatible profile can expose provider-defined nodes and groups that you can inspect, refresh, and select within Clash Verge Rev. That extra visibility is useful when you need to distinguish an expired subscription from an unavailable node or a profile-format problem, although it also means there are more settings to understand. If you want a client that supports this profile-based workflow, use the client download page to choose an appropriate build, then follow the provider’s instructions and keep the subscription URL private.
Ready to get started?
Choose a compatible client, import your provider’s remote profile, and keep its private URL secure.