How to Import an Airport Subscription Into Mihomo Party

Buying an airport plan is only the first step. The service usually gives you a subscription URL containing server nodes, authentication details, and transport parameters, but that URL does not automatically become an active proxy on your computer. You still need to import it into a compatible client, refresh the profile when the provider changes its nodes, choose a proxy group, and enable the system proxy. Mihomo Party makes this workflow relatively simple because it provides a graphical interface for Mihomo's profile and proxy-management features. This guide explains how to import an airport subscription into Mihomo Party, verify that it loaded correctly, update it safely, and troubleshoot the most common errors.

What You Need Before Importing

An airport subscription is normally represented by a long URL beginning with https://. Depending on the provider, it may be called a subscription link, subscribe URL, profile URL, or one-click import link. The link may return a YAML configuration directly, or it may return a provider-specific encoded list of proxy nodes that Mihomo Party converts into a usable profile.

Before opening Mihomo Party, prepare the following information:

• Your subscription URL: Copy the complete address from the provider's dashboard, email, or account page. Do not copy only the visible shortened text if the application displays the link inside a truncated field.
• Your subscription type: Confirm that the provider supports Clash, Clash Meta, Mihomo, or a compatible YAML format. A V2RayN-only, Shadowrocket-only, or WireGuard-only link may not work as a Mihomo profile.
• Your account status: Check that the plan is active and that you still have traffic or connection quota remaining. An expired plan can look like a client problem even when Mihomo Party is configured correctly.
• A current Mihomo Party installation: Use a recent build whenever possible. Older clients may not understand newer proxy types, transport fields, or provider-generated configuration syntax.
• A secure network for the first import: If the subscription link is blocked on your current network, downloading it through another trusted connection can help distinguish a network restriction from a malformed URL.

It is also worth saving a backup of any working profile before making major changes. Subscription profiles are usually overwritten during an update, while manually edited settings may be lost. Keep custom rules, DNS preferences, and local overrides in a separate note so they can be restored if necessary.

Import the Subscription in Mihomo Party

The exact labels can differ slightly between Mihomo Party releases, but the overall process is the same: open the profile page, add a remote profile, paste the URL, download the profile, and activate it. Do not paste the subscription into the proxy server list manually. A subscription is a complete remote source, not an individual node address.

1. Open Mihomo Party. Start the application and wait for the main window to finish loading. If it is minimized to the system tray, open the tray menu and select the main interface.
2. Go to Profiles. Select the profile or configuration-management section. This is where local YAML files and remote subscription sources are displayed.
3. Add a remote profile. Look for an option such as Add, New Profile, Import, or Download from URL. Choose the remote-URL option rather than a local-file option.
4. Paste the complete subscription URL. Make sure there are no spaces, quotation marks, line breaks, or extra characters before or after the address. If the provider supplies a dedicated Clash or Mihomo link, use that link instead of a generic format.
5. Give the profile a recognizable name. A name such as My Airport - Main or Airport - 2026 makes it easier to identify the profile later, especially if you use more than one provider.
6. Confirm and download. Mihomo Party should request the remote file and display a success message, node count, or profile entry. Wait until the download finishes before switching to another page.
7. Select the imported profile. Downloading a profile does not always activate it automatically. Click the new profile and use the application’s activate, use, or reload action if the interface provides one.

A successful import should produce more than a profile name. Open the profile details or proxy page and check whether the configuration contains proxy groups and individual nodes. A profile with zero proxies, an empty group, or only a parsing error is not ready for use. If the provider offers several subscription formats, the correct one normally contains words such as clash, clash-meta, or mihomo in its description.

https://provider.example.com/api/subscribe?token=YOUR_PRIVATE_TOKEN

The example above is only a structural illustration, not a real subscription. Never replace a provider's URL with a guessed address. Some services use a token in the query string, while others require an additional username, target parameter, or format selection. Always copy the URL generated by the provider.

Check the Imported Profile

After activation, inspect the profile before turning on global traffic. Look for a proxy group such as Proxy, PROXY, Auto, or a provider-created group. If the group contains several regions or transport types, the import has probably worked. If you see only DIRECT and REJECT, the provider may have returned a profile without nodes, or the subscription conversion service may have failed.

Do not immediately edit the downloaded YAML to fix a missing node. First test the original URL in a browser or with another trusted client. A provider may have temporarily disabled the subscription, reached its device limit, or returned an error page instead of YAML. Editing the client cannot repair a response that never contained a valid configuration.

Choose a Node and Enable the Proxy

Once the profile is active, importing alone is not enough. Mihomo Party must know which proxy group to use, and the operating system must send application traffic to the local Mihomo port.

1. Open the Proxies page. Find the main proxy group created by the subscription. Providers often place region groups inside a top-level selector, so you may need to choose the parent group first.
2. Select a usable node. Start with a nearby region or an automatically tested group. A lower latency value is useful, but it is not the same as real download speed. A node with slightly higher latency may perform better under load.
3. Run a health test if available. Use the latency or URL-test action to see whether nodes respond. A timeout can indicate a dead node, but a successful ping does not guarantee that HTTPS, streaming, or other applications will work.
4. Enable System Proxy. Turn on Mihomo Party’s system-proxy switch. This normally configures the operating system’s HTTP and HTTPS proxy settings to point to Mihomo’s local listener.
5. Enable TUN only when needed. TUN mode captures traffic from applications that do not respect ordinary system-proxy settings. It may require administrator permission and can interact with VPN software, security tools, virtual machines, and other network filters.
6. Test a simple website. Open a browser and visit a site that shows your public IP or a basic HTTPS page. Then test the services you actually need. One successful page does not prove that every application follows the same routing path.

The system-proxy switch and TUN mode solve different problems. System proxy is lightweight and is usually the best first choice for browsers and applications with HTTP or SOCKS support. TUN mode works at a lower network layer and can capture more traffic, but it also increases the chance of conflicts. If a browser works with System Proxy enabled, keep TUN disabled until you have a specific application that requires it.

Understand Proxy Groups

Airport profiles commonly include several layers of groups. A top-level group may contain regional groups, and each regional group may contain individual nodes. Selecting a node in a lower-level group may not change the actual route if the top-level group is still set to another option. When traffic appears to use the wrong server, follow the group hierarchy from the rule group down to the final node.

Some groups are automatic. A url-test group periodically checks a URL and selects a node with low measured latency. A fallback group keeps the first available node and switches only when it fails. A manual select group gives you direct control. Automatic groups are convenient, but their test URL may not represent the service you care about. If a node is fast for the test endpoint but slow for video or downloads, manually compare several nodes.

Update and Manage the Subscription

Airport nodes change frequently. Providers may add new servers, remove overloaded nodes, rotate credentials, or change transport parameters. You should refresh the subscription instead of repeatedly importing duplicate copies. In Mihomo Party, return to the profile list and use the update, refresh, or download-again action associated with the remote profile.

Before updating, note the following:

• Updating can replace the entire downloaded YAML file.
• Manually inserted nodes may disappear after the refresh.
• Custom rules or DNS edits inside the remote file may be overwritten.
• The provider may change group names, so previously selected groups may need to be selected again.
• A failed update may leave the old profile usable, depending on the client version and provider response.

If Mihomo Party supports profile scripting, local overrides, or a separate profile editor, use those mechanisms for personal changes rather than modifying the subscription source directly. Keep provider content and local preferences separate. This approach makes updates predictable and prevents a provider-side change from erasing your custom configuration.

A practical update routine is to refresh the profile once when you notice repeated failures, and then test the selected node before enabling TUN or changing DNS. If the old profile works and the new profile does not, compare the two versions if the client retains backups. The difference may reveal a removed node, an unsupported proxy type, or a changed group name.

Troubleshoot Common Subscription Errors

Most import failures fit into a small number of categories. Identify the exact stage that failed: copying the link, downloading the response, parsing the configuration, selecting a node, or routing application traffic. Each stage requires a different fix.

Fix Download and Format Errors

If the client reports a network error, first determine whether Mihomo Party can reach the subscription domain. Copy the URL into a browser. A valid response may download a file or display plain text; an account login page, CAPTCHA page, JSON error, or HTML error page is not a valid profile. Check for URL expiration, traffic limits, IP restrictions, and device-count limits in the provider account.

If the browser can open the link but Mihomo Party cannot, a local firewall, DNS problem, certificate issue, or application permission may be involved. Try another trusted network and update Mihomo Party. Avoid disabling certificate verification as a permanent workaround. A subscription URL contains account credentials, so it should be transferred over HTTPS and validated properly.

A parse error usually means the downloaded content is not valid for the selected client. Common causes include choosing a Base64, Surge, or Quantumult format instead of Clash/Mihomo; receiving a provider error page; or encountering a proxy type unsupported by an outdated Mihomo core. Select the provider's Mihomo or Clash Meta target, refresh the profile, and confirm that the client core is current.

Fix Connected but No Access

A green connection indicator only means that the local core is running or that a node test succeeded. It does not prove that your browser is using the intended group. Confirm that System Proxy is enabled, the top-level rule group points to a real node, and the application is not configured with a separate proxy. Browser extensions, corporate VPNs, and security software can override or intercept the operating system proxy.

If only some domains fail, inspect the active rule. A rule may intentionally send the domain to DIRECT, or a rule provider may be outdated. If every domain fails, test another node and check DNS. With TUN enabled, also look for conflicts with another VPN, virtualization software, or a firewall that blocks the virtual network interface. Disable TUN temporarily and retest using System Proxy alone.

When the connection is slow, avoid judging a node only by its displayed latency. Test several nodes at different times, close unused connections, and refresh the subscription if the provider has changed its server list. A crowded node, poor international routing, packet loss, or an unsuitable transport can all reduce performance even when the latency test looks acceptable.

A Reliable Daily Workflow

For routine use, keep the process simple. Store the subscription URL in a password manager, not in a public note. Maintain one clearly named remote profile per provider, and remove old duplicate profiles so you do not accidentally activate an expired copy. Update the active profile when nodes stop working, then select a node again if the provider has reorganized its groups.

Use System Proxy for ordinary browser traffic and enable TUN only for applications that need transparent capture. Keep a known-good node or group as a baseline for testing. When something breaks, return to that baseline, test the subscription download, verify the profile contents, check the selected group, and only then investigate DNS or advanced routing.

Once the subscription is imported and the basic route is confirmed, Mihomo Party can handle most day-to-day operations without manual YAML editing. You can switch nodes, run latency tests, refresh provider data, and inspect rules from the interface. This staged approach keeps the setup understandable: the subscription supplies the nodes, Mihomo provides the routing engine, and Mihomo Party provides the controls that connect the two.