How to Add an Airport Subscription to Clash Verge Rev

Before you import: check the subscription details

A newly purchased proxy plan usually arrives as a subscription URL, sometimes called an airport link, subscription link, or profile URL. In Clash Verge Rev, that URL is used to fetch a profile containing proxy nodes and, depending on the provider, rules, policy groups, and update settings. It is not the same thing as a single server address: importing the subscription normally adds a reusable profile that you can refresh later when the provider changes its configuration.

Start with the provider’s account page or delivery message, rather than copying a link from a chat preview. Check that the plan is active, that you have copied the complete URL, and that the provider says it is compatible with Clash or Mihomo. Some services issue separate links for different clients, formats, or account devices. A link intended for another client may return a page of instructions, a plain-text error, or a configuration that Clash Verge Rev cannot parse.

It also helps to know what kind of address you received. A subscription URL often contains a long token or account identifier, and anyone with access to it may be able to use your traffic allowance. Treat it like a password. Do not paste it into public issue trackers, screenshots, shared documents, or online URL-testing tools. If you need support, first ask the provider whether they can identify the failed request from your account; if you must share a diagnostic, remove the token and any identifying query parameters.

Before changing settings, note the provider’s refresh limits and device policy. Some providers restrict how frequently a profile can be fetched, while others count active devices or bind access to a particular account. Repeatedly clicking refresh is rarely a useful first response to an import error; it can trigger rate limiting without fixing a typo, expired plan, or captive-portal problem.

Add the subscription as a profile

Open Clash Verge Rev and go to the Profiles view. Depending on the version and window layout, the action for adding a profile may appear as a plus icon, an add button, or a URL import option. Choose the option for adding a remote profile or subscription rather than creating a local file. Labels can differ slightly between releases, so identify the action by its purpose instead of relying on one exact button name.

1. Copy the full subscription URL from the provider’s trusted account page. Avoid copying surrounding punctuation, quotation marks, or a trailing space from an email or messaging app.
2. In Clash Verge Rev, open Profiles and choose the option to add a profile from a URL. If the dialog asks for a name, enter a short label that helps you recognize the provider or plan without exposing the private URL.
3. Paste the URL into the address field. If the app offers a separate display-name field, use that field for your label; do not alter the URL to make it look more readable.
4. Confirm the import or add action, then wait for the profile request to finish. A successful request should create a profile entry. Select that entry if the interface does not activate it automatically.

Importing and using a profile are separate actions. The profile can exist in the list while another profile remains active, so check the selected or active indicator after the request completes. If the dialog asks whether to replace a profile, read the prompt carefully: replacing a local configuration may discard settings you have maintained yourself. A new subscription is usually best added as a separate profile unless you specifically intend to replace an existing one.

The profile name is only a local label; it does not change the provider’s configuration or grant additional access. If you maintain several subscriptions, choose names that distinguish their purpose, such as “Personal plan” or “Travel plan,” rather than names that expose account email addresses or order numbers. This makes later refreshes easier to identify and reduces the chance of selecting the wrong profile when comparing providers.

Load the profile and select a node

After adding the profile, give Clash Verge Rev time to download and parse its contents. The visible result varies by provider: some subscriptions include many individual nodes and several policy groups, while others expose only a compact set of choices. A profile that imported successfully but contains no usable proxies may still be an account, format, or provider-side issue rather than a problem with the node selector.

Open the proxy or groups view and inspect the groups provided by the configuration. A group may be named for a purpose such as automatic selection, fallback, or a region. Selecting a group is not always the same as selecting a specific server: if the group is a selector, open it and choose one of its listed members. If it is an automatic-testing group, the core may choose a member based on its health checks, so a displayed choice can change after a test or refresh.

For a first connection test, choose a clearly listed node or a provider-supported automatic group, then allow a little time for the selection to take effect. A low latency value is not a complete quality score. It usually reflects a particular probe to a particular test endpoint, not every website, streaming service, or application you might use. If a node looks fast but an application cannot connect, test another provider-listed option and compare the result under the same conditions.

Keep the first test simple. Use a normal browser or another application whose proxy behavior you understand, and confirm that the profile is selected before changing rules, DNS options, or tunnel settings. Changing several settings at once makes it difficult to tell whether the subscription, selected node, local listener, or application behavior caused the result.

Refresh the subscription without losing track of changes

A subscription profile is normally refreshed from the profile list, using a refresh or update action associated with that entry. Refreshing asks the provider for the current configuration; it may update node names, server addresses, policy groups, or rules. It does not necessarily reset every local setting, and it may not preserve a manually selected node if that node was removed or renamed upstream.

When a provider announces a configuration change, refresh the intended profile once and wait for the operation to finish. Then confirm that the same profile remains active, inspect the groups again, and choose a current node if the old selection is no longer present. If your connection was working before the update, make a note of the selected profile and node first. That small record makes it easier to distinguish a provider-side change from a local change if the result is different afterward.

Avoid refreshing several times in rapid succession. A slow response may reflect a busy provider endpoint, an unstable Wi-Fi connection, or an account limit. Repeated requests can add noise to the diagnosis and may cause a provider to temporarily reject further requests. If the profile update completes but traffic stops working, first test a different available node and verify that your local network still has internet access before editing configuration options.

If you also use a local configuration, keep it separate from the remote subscription unless you understand how the application handles merges and overrides. A locally edited copy can become stale when the provider changes its format, while replacing a remote profile with a local file can make later updates appear to have no effect. For routine use, treat the subscription as the provider-maintained source and keep any personal changes in a deliberate, documented configuration workflow.

Troubleshoot failed imports step by step

When a profile fails to import, read the full status message before changing anything. “Request failed,” “invalid response,” and “parse error” point to different stages. A request failure suggests that the client could not retrieve a usable response. An invalid response may indicate that the provider returned an account notice, an expired-plan page, or a blocked-request message instead of a subscription. A parse error means data arrived but did not match the format expected by the client.

1. Check the URL itself. Return to the provider’s account page and copy the current link again. Make sure the link was not truncated, line-wrapped, or altered by a browser, email client, or password manager.
2. Confirm account and plan status. Sign in to the provider’s official portal and check activation, expiration, remaining allowance, and any device or request limits. A payment confirmation message does not always mean the subscription has finished provisioning.
3. Check basic network access. Confirm that the computer can reach ordinary websites and complete any hotel, campus, or café Wi-Fi sign-in page. A captive portal can interrupt the profile request even when the network icon says connected.
4. Verify client compatibility. Ask the provider which client format is supported and whether a specific subscription link should be used for Clash Verge Rev. Do not assume that every link labeled “VPN” is a Clash-compatible configuration.
5. Retry once after correcting a likely cause. If the provider confirms the plan is active and the link is current, retry the import. If it still fails, note the time, app version, operating system, and exact error wording for support.

A failed import does not usually require reinstalling Clash Verge Rev. Reinstalling can remove useful local state while leaving the real cause untouched, such as an expired URL, a provider outage, a DNS problem, or a security product blocking the request. Similarly, changing core settings or editing a downloaded configuration before you know what failed can turn a simple account issue into a harder-to-reproduce client issue.

When contacting support, describe the stage that failed: whether the profile entry was created, whether nodes appeared, and whether the failure happened during import, refresh, or connection testing. Include the error text and a timestamp, but redact the subscription URL, tokens, account identifiers, and any private IP information. If support asks for a configuration file, inspect it first; remote profiles can contain account-specific values, and sharing the complete file may reveal details you did not intend to disclose.

Keep the setup reliable and private

Once the profile works, keep a short record of the provider name, the profile label used in Clash Verge Rev, and the date you last confirmed a successful refresh. Do not store the secret URL in that note. Put it in a password manager or the provider’s secure account portal, and keep screenshots limited to the interface details needed for troubleshooting. If a link is exposed, use the provider’s revocation or regeneration process rather than assuming that deleting a message makes the old link harmless.

For everyday use, change one thing at a time. If a connection stops working after a refresh, confirm which profile is active, check whether the selected node still exists, and test another provider-listed choice. If only one application fails, check whether it follows the system proxy or has its own proxy settings. If all applications fail, verify ordinary internet access before deciding that the subscription itself is broken. This sequence narrows the cause without turning a working configuration into an experiment.

The same troubleshooting discipline helps when moving between desktop clients. Clash Verge Rev gives you a profile-oriented workflow, visible groups, and a practical way to refresh a provider configuration; a generic system VPN app may hide those details, while manually maintaining a raw YAML file can make routine provider updates more error-prone. If you want to manage subscriptions, inspect nodes, and keep refreshes understandable in one place, Clash V.CORE offers a focused Clash client workflow for those tasks. You can download Clash V.CORE and use the same privacy-first checks when adding your next provider profile.