1. Before you import: what an airport subscription contains
An “airport subscription” is a provider’s link for retrieving proxy server details and, in many cases, a Clash-compatible configuration. In Clash Verge Rev, you can add that link as a remote profile, then select the profile and choose a proxy for your traffic. The link is usually different from an individual node address: it may contain an access token that lets the provider identify your account and return your current servers.
Ask your provider for the subscription format intended for Clash, Clash Meta, or Mihomo. A link for another client may return a different format, even if it comes from the same service. If the provider offers several subscription types, use the one that explicitly supports Clash or Mihomo rather than guessing from a filename or copying a link labeled for a different app.
Treat the full URL like a password. Anyone who obtains it may be able to download your profile or use the service associated with your account. Do not post it in a screenshot, public support channel, shared document, or diagnostic log. If you think it has been exposed, use the provider’s dashboard to reset or regenerate the subscription link, then replace the saved URL in Verge Rev.
Before proceeding, check that Clash Verge Rev is installed and can start normally. You will also need an active subscription URL, an internet connection that can reach the provider, and a provider account that has not expired or exceeded its limits. A working link does not guarantee that every returned node is online: importing retrieves profile data, while using a proxy also depends on the selected server and your network’s ability to connect to it.
2. Add the subscription in Clash Verge Rev
The exact labels and layout can differ slightly between Clash Verge Rev releases, but the workflow is the same: open the profile management area, create a remote profile, enter the subscription URL, and fetch its contents. If a button name differs from the steps below, look for the control that adds a profile from a URL; do not paste a credential link into a YAML editor or a node-import box.
-
Copy the correct URL. Sign in to your provider’s website or dashboard and copy the Clash or Mihomo subscription address. Copy the complete link, including its scheme such as
https://and any query parameters after the question mark. Avoid adding spaces or punctuation when selecting it. -
Open Profiles. Launch Clash Verge Rev and go to the page or panel used to manage profiles. Choose the option to add a profile from a URL or subscription. If you see separate options for a local file and a remote URL, choose the remote option.
-
Enter the URL and a useful name. Paste the full address into the URL field. Give the profile a recognizable name, such as the provider name or the plan name. A descriptive name helps when you later compare profiles, but do not put the private URL itself in the name.
-
Fetch the profile. Confirm the entry and use the download, update, or fetch control presented by your version. Wait for the request to finish. A successful result should appear in the profile list, usually with a timestamp, status, or profile details.
-
Select the imported profile. Adding a profile and using it are separate actions. Select or activate the new profile in the profile list. If it is not active, Verge Rev may continue using a different profile even though the import succeeded.
-
Choose a proxy and test it. Open the proxy or connection view, select a provider node or group, and make a simple connection test. Check that the application shows the intended profile as active before interpreting a failed test as a bad subscription.
Some providers supply a URL that returns a full Mihomo YAML configuration; others return a list of nodes that the client incorporates into a generated profile. Those formats can produce different views after import. If the profile is present but you cannot find a familiar server name, check the provider’s documentation for how it names groups and whether the returned configuration is intended to be used directly or combined with another configuration.
3. Verify the profile and keep it current
After importing, take a moment to confirm that the saved profile is the one you intended. Check its name, whether the last update completed, and whether the proxy list or configuration contains expected entries. If the provider publishes a server count or plan label, compare it with what Verge Rev displays. A difference is a reason to investigate, not immediate proof that the client is broken: providers may change node availability, regions, or profile contents without changing the subscription URL.
To refresh the profile later, return to the profile manager and use the update or refresh action for that entry. You normally do not need to create a second profile every time the provider changes its servers. Repeatedly adding the same URL can leave you with several entries that look alike, making it unclear which one is active. If you intentionally keep multiple plans or accounts, give each profile a distinct name and remove only the entries you have confirmed are obsolete.
An update request downloads profile data; it does not necessarily change the selected proxy or guarantee that an existing connection is restarted. If the profile refreshes successfully but an application continues to use an old route, verify the active profile and proxy selection, then retry the application’s connection. For a clean comparison, note the profile’s update time and test one node at a time rather than switching several settings at once.
Automatic refresh behavior can depend on the client version and profile settings. If Verge Rev exposes an interval or scheduling option, use a sensible value that follows the provider’s guidance. Refreshing very frequently rarely makes a server more available and can create unnecessary requests. If automatic updates are not offered or you prefer manual control, use the profile’s refresh action when the provider announces a change or when the current list appears stale.
A subscription URL and a local configuration file are not interchangeable in every workflow. A URL is useful when the provider maintains the remote profile and expects the client to fetch updates. A local file is appropriate when you have been given a YAML configuration that you intend to manage yourself. Do not overwrite a remote profile with a locally edited file unless you understand how your client and provider expect updates to work; the next refresh may replace local changes with the provider’s version.
4. Troubleshoot invalid links, unsupported formats, and failed updates
Start with the exact stage that failed. “Could not add profile,” “download failed,” “configuration parse error,” and “proxy test failed” describe different problems. Retrying the same action without identifying the stage can obscure the cause. Check the displayed error, the profile’s update time, and whether the profile entry was created before changing the URL or client settings.
| Symptom | Likely cause | What to check |
|---|---|---|
| The URL is rejected immediately | Incomplete link, pasted whitespace, or the wrong type of address | Copy the Clash or Mihomo subscription URL again from the provider dashboard. |
| The request returns an error or no data | Expired account, invalidated token, provider outage, or unreachable server | Check account status and provider notices, then try the link in the client again without sharing it. |
| The profile downloads but cannot be parsed | The endpoint returned an unsupported client format or malformed configuration | Confirm that the provider offers a Clash/Mihomo format and ask for a compatible subscription link. |
| Import works, but a proxy test fails | The selected node is unavailable, the profile is not active, or the local network blocks the connection | Verify the active profile, test another provider node, and check Verge Rev’s connection status. |
| An update stays pending or times out | Temporary connectivity trouble, DNS failure, provider-side load, or a blocked request | Retry once, check ordinary internet access, and consult the provider’s service status before making repeated requests. |
Check the URL and account first
A subscription link can look valid while its token has expired or been reset. Return to the provider dashboard and copy the currently displayed URL rather than relying on an old message or browser bookmark. Make sure the account is active and that the service has not reached a device, traffic, or renewal limit. If the provider supports regenerating a link, use that option only when needed: replacing the URL may invalidate the previous one, so update Verge Rev after you regenerate it.
If the link opens a web page, returns a login screen, or downloads a document that is clearly for a different client, the issue may be the endpoint rather than the clipboard. Providers sometimes publish separate links for different applications. Ask which endpoint is intended for Clash Verge Rev and avoid manually editing the URL to guess at a format.
Check format and connectivity
A parser error usually means that the response was received but could not be interpreted as a supported profile. This can happen when a provider changes formats, the link serves an HTML error page instead of configuration data, or the response is truncated. Confirm the client type in the provider’s instructions and update Clash Verge Rev through a trusted distribution source if the provider requires a newer Mihomo-compatible client. Do not attempt to fix an unfamiliar configuration by deleting lines at random; that can create a profile that imports but routes traffic incorrectly.
If the update times out, check whether other websites load and whether the provider reports an outage. A local DNS issue, restrictive network, or temporary service problem can interrupt the request even when the URL is correct. Retry after a short wait, and compare from another permitted network if available. Avoid repeatedly refreshing in quick succession, which can add load without distinguishing a provider outage from a local connection problem.
When asking for help, provide the client version, operating system, time of the failed request, and the exact error message with the subscription URL removed. If you share a log, search it for the full token and redact it before sending. A screenshot can also expose account names, server addresses, or access credentials, so review it carefully before posting.
5. Common questions
Is a subscription URL the same as a node link?
No. A subscription URL commonly retrieves a profile or a set of nodes and may include an account token. A node link usually describes an individual connection. Use the import method and format that the provider specifies; importing a single-node link as if it were a subscription may fail or produce a different result.
Why did the profile import but my traffic did not change?
Importing saves profile data, but you may still need to select the profile and choose a proxy group or node. Check that the expected profile is active, then review the connection view and test a node. Also remember that an application may need to reconnect before it uses the newly selected route.
How often should I refresh the subscription?
Follow the provider’s recommendation or use the client’s available update schedule. Manual refresh is usually enough when you are troubleshooting or when the provider announces changes. Very frequent refreshes do not improve the connection quality of a node and may send unnecessary requests to the provider.
Can I send my subscription URL to support?
Avoid sending the complete URL unless the provider explicitly requests it through a secure support channel. The link may grant access to your profile or account. Start by sharing the error text and client version with the URL removed; if support needs to inspect the credential, ask for a safe submission method or regenerate the link afterward.
6. A repeatable workflow beats trial and error
A one-click VPN-style client can be convenient, but it may reveal little about whether a subscription was fetched, which profile is active, or why a particular update failed. Managing a provider URL directly in Clash Verge Rev takes a few more deliberate checks, yet gives you a clear profile list, an explicit refresh action, and the ability to select and test individual proxies. Those details make it easier to separate an invalid link from an unavailable node or a temporary network problem. If you want a client download and a guided starting point for this workflow, use the links below.
Ready to get started?
Choose a compatible client, add your provider’s subscription, and keep the profile easy to refresh.