An airport subscription is a URL that lets a proxy client download and refresh a provider’s configuration, including its nodes and, in some cases, proxy groups and routing rules. In Clash Verge Rev, importing that URL creates a profile you can select and update from the desktop interface. This guide explains how to add an airport subscription, confirm that the profile loaded correctly, test node connectivity, and troubleshoot common import failures without exposing your subscription credentials.
Before You Import a Subscription
Before opening Clash Verge Rev, make sure you have the correct subscription URL from your provider. A subscription link is not usually the same as the provider’s website address, account login page, or a link to a single node. It is a credential-bearing URL that lets the client retrieve your subscription data. Depending on the provider, it may contain a token or other identifying information in its path or query string.
Copy the URL from the provider’s official dashboard or setup instructions. If the provider offers several links for different clients or formats, choose one intended for Clash, Clash.Meta, Mihomo, or Clash Verge Rev. Providers sometimes label these links as “Clash subscription,” “Mihomo configuration,” or “universal subscription.” The exact naming varies, and not every link is compatible with every client.
- Check the client version: Use a current Clash Verge Rev release and a compatible Mihomo core. An older core may not understand newer proxy protocols or configuration fields used by the provider.
- Keep the URL private: Treat it like a password. Do not post it in screenshots, public forums, support tickets visible to other users, or online URL-conversion services.
- Review the provider’s usage notes: Some services require a particular subscription format, user agent, or conversion option. Follow those instructions if they differ from a generic setup.
- Check your network: The first import requires the client to reach the provider’s subscription server. A captive portal, restrictive network, or temporary DNS problem can prevent the download.
It is also useful to know what the subscription is expected to contain. A provider may return a complete Clash configuration, a list of proxy nodes, or data that the client converts into a profile. A successful download does not necessarily mean that every node is online, that a proxy group has the selection you expect, or that system traffic is already being routed through the client. Import, connection testing, and traffic routing are separate checks.
Add the Subscription URL in Clash Verge Rev
The interface labels can differ slightly between Clash Verge Rev releases and operating systems, but the general workflow is the same: open the profile-management area, create a remote profile, enter the URL, and download the configuration. Do not paste the link into a local configuration editor unless your provider specifically instructs you to do so. A remote profile is designed to remember its source and can be refreshed later.
- Open Clash Verge Rev. Wait for the main window to finish loading. If the application reports that its core is unavailable, resolve that issue first; a profile may download successfully while core functions remain unavailable.
- Go to Profiles. Select the section used to manage configurations or profiles. Depending on the release, this may appear in the sidebar or as a profile-management view.
- Add a remote profile. Choose the action for adding a profile by URL, adding a remote configuration, or creating a subscription. Avoid options intended for importing a local YAML file.
- Enter the subscription address. Paste the complete URL copied from the provider. Check that it has not been truncated and that no extra spaces or line breaks were included at the beginning or end.
- Give the profile a recognizable name. A provider name or a neutral label such as “Personal subscription” makes it easier to distinguish this profile from local test configurations. Avoid putting private account details in the name.
- Save or confirm the profile. The client should request the remote configuration. Keep the application open while the request completes, especially on a slow connection.
After the download, look for the new profile in the list. A profile may show a success indicator, a recent update time, or a summary of its contents. If it is listed but has no usable proxies, do not assume that the subscription URL is valid merely because the profile entry exists. Open the profile details or inspect the client’s logs to confirm that configuration parsing finished without errors.
If the interface asks for a converter or subscription format, use the provider’s recommended option rather than experimenting with unrelated converters. A converter can transform, filter, or rename configuration data. Incorrect converter settings may remove proxy groups, alter rule behavior, or make an otherwise valid subscription appear incomplete. When unsure, first try the provider’s direct Clash-compatible URL.
Select the Profile and Check Its Contents
Downloading a profile and using it are two different actions. In the profile list, select the newly imported profile and use the interface’s activation or switch action if it is not already active. Some versions select a profile as soon as it is added; others require an explicit action. Confirm that the active-profile indicator points to the subscription you intend to use before changing system proxy settings.
Next, open the proxy or node view. A populated subscription usually provides one or more proxy entries and may also include groups such as an automatic selection group, a region group, or a manual selector. The names and structure are controlled by the provider, so they may not match examples shown in other guides. If the profile contains proxy groups, inspect the group first and select a node within it when manual selection is available.
- Confirm that entries are present: An empty node list can indicate a failed download, an incompatible format, expired access, or a provider-side issue.
- Read the group names: A group can be a selector, an automatic latency test, or a failover group. A group name alone does not guarantee that a specific node has been selected.
- Check whether the profile includes rules: A complete configuration may include routing rules and DNS settings. A node-only subscription may rely on the client’s existing configuration or provider-defined defaults.
- Look for parse errors: Warnings about unsupported fields, missing values, or invalid YAML can explain why the profile appears incomplete.
Do not edit a provider-managed profile directly unless you understand how updates are applied. A remote refresh can replace downloaded content, so manual changes made inside a generated configuration may be lost. If you need custom routing or DNS behavior, use the client’s supported override or merge features when available, or keep a separate local configuration for changes that must persist.
Refresh the Profile and Test Connectivity
Subscriptions can change as a provider adds nodes, removes unavailable servers, or updates configuration data. To fetch the latest version, return to the profile-management view and use the refresh or update action for the imported profile. Wait for the request to finish and check the update status. A profile that updates successfully should retain its identity while refreshing the remote data, although the available nodes or groups may change.
Use the following sequence to verify the setup after importing or refreshing:
- Confirm that the profile is active. The current profile should be the one created from the subscription URL, not an older local or remote profile.
- Choose a proxy group or node. If the provider supplies a manual selector, select a node. If the provider supplies an automatic group, wait for its tests or use its selection controls as intended.
- Run a delay test. Use the client’s latency-test function if available. A delay result indicates that a test request received a response; it does not prove that every website, app, or protocol will work through that node.
- Enable the appropriate traffic mode. Depending on your goal, select the system proxy mode or configure TUN mode. System proxy settings generally affect applications that honor the operating system’s proxy configuration; TUN mode can capture a broader range of traffic but may require additional permissions.
- Test a real destination. Open a site or application that should use the selected route, then check the client’s connection or log view to see which rule and proxy group handled the request.
A successful delay test only checks reachability to the test endpoint. It does not verify subscription quota, account status, routing rules, DNS behavior, or access to every service. If a test reports a timeout, try another node and, if the client permits it, another test destination. Latency results can also vary due to the current network path, server load, and the test URL itself.
Keep track of which mode you enabled. If the node tests successfully but a browser still connects directly, the system proxy may be disabled, the browser may be using a separate proxy setting, or the active rule may route that destination to DIRECT. If some applications work and others do not, that often points to differences in how those applications handle system proxies rather than a failed subscription import.
Troubleshoot Common Import Problems
When an import fails, identify which stage is failing: reaching the subscription server, receiving the response, parsing the configuration, activating the profile, or routing traffic. This distinction prevents unnecessary edits. For example, changing a proxy group cannot fix a subscription server that is unreachable, while repeatedly re-entering a valid URL will not resolve a YAML parsing error.
- “Invalid URL” or immediate validation failure: Recopy the complete address from the provider dashboard. Remove accidental spaces, quotation marks, or punctuation added when copying. Confirm that you selected the subscription link rather than a web login page.
- Timeout or network error: Check whether the device has internet access, whether a captive portal needs to be completed, and whether the provider’s subscription server is reachable from the current network. If you are already using another proxy, test carefully; a circular setup in which Clash must use the profile to fetch the profile can prevent the initial request.
- HTTP authorization or expired-link error: Sign in to the provider account and check the subscription status, expiration, device limit, and available traffic. Generate a replacement link if the provider reports that the current one has been revoked or is no longer valid.
- Download succeeds but no nodes appear: Verify that the URL is for a Clash-compatible format and that the provider has assigned usable nodes to the account. Review the response or application log for conversion and parsing errors.
- Unsupported protocol or configuration field: Update Clash Verge Rev and its Mihomo core when a supported update is available. If the provider recently changed formats, request a compatible subscription link instead of deleting fields at random.
- Nodes appear but tests fail: Try more than one node, check the test method and network environment, and verify that the account remains active. A failed test can be caused by a temporary outage or a blocked test destination, not only by an invalid profile.
- The profile updates but changes do not appear: Make sure you refreshed the correct profile, wait for the update operation to complete, and reopen the node or group view. Some providers may return the same configuration until they publish a change.
- Traffic still does not use the proxy: Check that the intended profile is active, a usable node is selected, and system proxy or TUN mode is enabled as appropriate. Inspect the connection log and routing rule for the affected destination.
Logs are most useful when you inspect them immediately after reproducing the problem. Note the error message, timestamp, client version, core version, and whether the failure happened during download, parsing, or connection testing. If you contact the provider, share only the diagnostic details they need. Redact subscription URLs, tokens, account identifiers, and any configuration values that could grant access.
Avoid pasting a private subscription link into public “subscription conversion” websites to test whether it works. Such a service may be able to read and retain the URL or its configuration. Prefer the provider’s own tools and the client’s built-in logs. If a provider explicitly recommends a converter, verify that the address belongs to the provider or to a service the provider trusts.
Keep the Subscription Reliable and Secure
Once the subscription works, use the client’s update control when the provider publishes changes, and follow any refresh interval recommended by the provider. Refreshing too often is rarely helpful and may count toward request limits or trigger rate limiting. If the profile is stable, let automatic update behavior handle routine maintenance where supported; perform a manual refresh when a provider announces a change or when a known configuration issue has been fixed.
Keep a simple record of the profile’s display name, the date you last confirmed an update, and which broad traffic mode you use. Do not store the full subscription URL in an unprotected note. If you migrate to another computer, retrieve a fresh link from the provider account rather than sending the old one through chat or email. When removing an unused profile, remember that deleting it from the client may not revoke the underlying link; revoke it separately in the provider dashboard if access should end.
If a profile breaks after an update, first check the provider’s service status and refresh result. Then confirm whether the provider changed its subscription format or whether the client core needs an update. Keep changes reversible: note the previous mode or group selection before changing settings, and avoid replacing the provider configuration with an unrelated sample file. A clear baseline makes recovery faster and helps support teams identify the real cause.
With the URL added, the profile selected, and a real connection checked, the essential setup is complete. You can now update the profile when needed and troubleshoot future issues by separating download, parsing, node reachability, and traffic-routing checks. If you still need the client itself or want a broader setup walkthrough, use the links below to continue with the appropriate guide.
Take Full Control of Your Traffic with Clash
Available on Windows, macOS, Linux, Android, and iOS. Flexible rules, simple setup, ready to use.