Mihomo Party Setup Guide: Add Subscriptions And Switch Nodes
Understand the Mihomo Party setup flow
Mihomo Party is a graphical client that uses the Mihomo proxy core to load configuration files, create local proxy ports, apply routing rules, and connect to remote proxy nodes. Installing the application is only the first step. A fresh installation normally has no usable subscription, no imported YAML profile, and no selected node, so opening the main window does not automatically provide a working connection.
A complete setup has several separate stages. First, you need a subscription URL or a local configuration file from your service provider. Next, Mihomo Party must download or read that configuration and make it the active profile. The configuration then supplies proxy nodes, proxy groups, DNS settings, and routing rules. Finally, you select a proxy group or node, enable the appropriate traffic mode, and test a destination that should pass through the proxy.
These stages are related but should not be confused. A subscription can download successfully while every node is unavailable. A node can show a low latency while the system proxy is disabled. A profile can load without errors while its rules send the tested domain directly. Troubleshooting becomes much faster when you verify the profile, node, group, mode, and application traffic path separately.
Subscription
A URL used to retrieve an updated configuration containing nodes, groups, rules, and sometimes DNS settings.
Proxy node
A server entry with a protocol, address, port, and credentials that the Mihomo core can use as an exit.
Proxy group
A collection of nodes or policies used by rules and the interface to decide how traffic should be handled.
Add a subscription or local profile
Open Mihomo Party and look for the profile or configuration management area. The exact label can differ between releases, but the workflow is usually based on adding a remote URL, assigning a local name, and downloading the resulting configuration. Do not paste a subscription URL into a node field or into the YAML editor. A subscription URL is a source for an entire profile, not the address of one proxy server.
Import a remote subscription
- Copy the subscription URL from your provider’s account page. Copy the full address, including any query string or access token.
- In Mihomo Party, open the Profiles or configuration management page and choose the option to add a remote profile.
- Paste the URL into the subscription field and enter a recognizable name such as
Home-mainorWork-backup. - Save the profile, then use the update or refresh action to download its latest content.
- Click the downloaded profile to make it active. An imported profile is not necessarily the currently running profile until it is selected or activated.
After the download finishes, inspect the profile summary before testing traffic. A useful profile should expose one or more proxies and proxy groups. If Mihomo Party reports an HTTP error, timeout, unauthorized response, or empty body, the problem is at the subscription retrieval stage rather than the node-selection stage. Check the URL, account status, network access, and any provider-side device or traffic limit.
Import a local YAML file
If your provider gives you a YAML file instead of a URL, choose the local profile or file import option. Keep the original file as a backup before making edits. Mihomo configuration files commonly contain sections such as proxies, proxy-groups, rules, and dns. YAML indentation is significant: use spaces rather than tabs, keep list items aligned, and quote values containing characters that may be interpreted as YAML syntax.
mixed-port: 7890
mode: rule
proxies:
- name: "Example Node"
type: socks5
server: example.invalid
port: 443
proxy-groups:
- name: "Proxy"
type: select
proxies:
- "Example Node"
- DIRECT
rules:
- MATCH,Proxy
This is only a structural example and does not provide a real connection. A subscription-generated configuration may be rebuilt whenever you update it. Therefore, persistent changes should normally be made through Mihomo Party’s supported overrides or the provider’s configuration options instead of editing a generated file directly.
Update the profile and verify its contents
Subscription providers change node addresses, certificates, ports, and availability over time. A profile that worked last week may still be present in Mihomo Party but contain expired or removed servers. Use the profile’s update action whenever the provider publishes a new configuration or when several nodes suddenly stop working.
Before updating, note any local changes you made. If the client uses an override, merge, or patch mechanism, confirm that the override is attached to the correct profile. If you manually edited the downloaded YAML, save a copy first because the next update may replace it. After updating, activate the refreshed profile and check whether the expected proxy group still exists.
| What you see | Likely meaning | Next action |
|---|---|---|
| Update succeeds and nodes appear | The subscription was retrieved and parsed | Activate the profile, then select a group and node |
| HTTP 401 or 403 | The URL is unauthorized, expired, or restricted | Generate a new URL or check the provider account |
| Timeout or connection reset | The subscription endpoint cannot be reached | Test the endpoint in a browser and check the current network path |
| Download succeeds but no proxies appear | The response is empty, incompatible, or incorrectly converted | Inspect the provider format and Mihomo core compatibility |
| Profile loads but the group is empty | Group names do not match node or provider references | Review the YAML references and the active profile |
Do not use a successful update as proof that proxy traffic works. The update request may be allowed directly by the network, may use a browser path, or may return a valid file even though the nodes inside it are unreachable. The meaningful test comes after the profile is active, a proxy group has been selected, and a request appears in the Mihomo Party connection log.
Select a working proxy node
Open the proxy or groups view after activating the profile. Most usable configurations contain a main group with a name such as Proxy, 节点选择, Final, or a provider-specific label. A group may contain individual nodes, another nested group, and the DIRECT option. The rule list decides which group handles each destination; changing a node inside the group changes the exit used by traffic already assigned to that group.
Click a group and choose an individual node, or choose an automatic policy such as URL testing or latency-based selection if the group supports it. A latency number is useful for screening, but it is not a complete quality measurement. The test may use a particular URL and timeout, while the destination you care about may use a different protocol, port, geographic restriction, or authentication path.
A practical node selection method
- Start with a node that reports a recent successful test rather than one with a stale or blank result.
- Prefer a moderate latency with stable repeated tests over the lowest single result.
- Test two or three nodes from different regions if the first connection fails.
- After selecting a node, open the connection log and confirm that the target domain is assigned to the expected group.
- Keep the selected node only if the actual service works; do not judge it by latency alone.
If the group displays no selectable nodes, inspect the active profile rather than repeatedly refreshing the interface. The group may reference a proxy provider that failed to load, a node name that changed during the update, or a group excluded by a filter. A node marked alive can also fail later because the remote server is overloaded, the account has reached its limit, or the target service rejects that exit address.
Choose the right traffic mode
Mihomo commonly provides Rule, Global, and Direct modes. The mode determines how the core handles traffic after it enters Mihomo, but it does not replace the system proxy switch or TUN permission.
| Mode | How traffic is handled | Best use | Important limitation |
|---|---|---|---|
| Rule | Evaluates rules from top to bottom and sends traffic to a group, directly, or to reject | Normal daily use and domain-based split routing | Incorrect rules or rule data can produce unexpected routing |
| Global | Sends traffic handled by the core to the selected global proxy group | Short troubleshooting tests or forcing a single exit | It may proxy destinations that should normally be direct |
| Direct | Attempts to connect without using a proxy node | Testing the local network or restoring direct access | It does not solve a destination that requires proxy access |
For most users, start with Rule mode. In Rule mode, check the connection details for the domain you are testing. The log should show whether the request matched a proxy group, DIRECT, or REJECT. If a service is unexpectedly direct, the relevant rule may be missing, placed below a broad MATCH,DIRECT rule, or affected by a domain or IP classification database.
Global mode is useful as a diagnostic comparison. If the same application works in Global mode but not in Rule mode, the selected node is probably usable and the issue is more likely related to rule order, rule providers, DNS behavior, or a group selection. Do not leave Global mode enabled permanently without understanding its effect on local services, banking sites, intranet addresses, and bandwidth usage.
Direct mode helps determine whether the underlying network works without Mihomo. It can also prevent accidental proxying while you edit a profile. Changing the mode affects traffic that already enters the Mihomo core; applications that ignore the system proxy may continue to connect directly until you configure their own proxy settings or enable a suitable TUN mode.
Enable system proxy or TUN only when needed
The system proxy switch and the Mihomo traffic mode perform different jobs. The system proxy tells applications that support the operating system proxy settings to send requests to Mihomo’s local HTTP or mixed port. TUN creates a virtual network interface and can capture traffic from applications that do not understand system proxy settings, but it requires additional permissions and may interact with DNS, firewalls, VPN software, and endpoint security tools.
For an initial setup, enable the system proxy first and test with an application known to follow it, such as a browser without an independent proxy extension. Check the local port shown in Mihomo Party rather than assuming it is 7890. A typical configuration might contain:
mixed-port: 7890
socks-port: 7891
allow-lan: false
mode: rule
The values above are examples, not requirements. If another application already uses port 7890, Mihomo may fail to start its listener or may use a different port. If you want to configure a terminal manually, use the actual HTTP or mixed port reported by the running client:
# HTTP-style proxy variables
export HTTP_PROXY=http://127.0.0.1:7890
export HTTPS_PROXY=http://127.0.0.1:7890
# Clear them when testing a direct connection
unset HTTP_PROXY HTTPS_PROXY
On Windows PowerShell, the equivalent temporary variables can be set with $env:HTTP_PROXY="http://127.0.0.1:7890" and $env:HTTPS_PROXY="http://127.0.0.1:7890". Some tools use uppercase variables, lowercase variables, or their own proxy flags, and some protocols such as Git over SSH do not automatically use an HTTP proxy. A successful browser test therefore does not prove that every terminal program is routed through Mihomo.
Use TUN after the basic system-proxy path works. Grant the requested administrator or system extension permission, avoid running several VPN or transparent-proxy tools at the same time, and review the client log after enabling it. If TUN causes DNS failures, duplicated routes, or loss of local network access, disable it temporarily and return to the simpler system-proxy test path.
Troubleshoot the most common setup failures
The subscription will not update
First copy the URL into a browser or another controlled HTTP client only to check whether the endpoint responds; do not publish the URL. A login page, JSON error, HTML error document, HTTP 401, HTTP 403, or an expired-token message indicates a provider or account problem. A timeout may indicate that the endpoint is unreachable from the current network. If the URL opens but Mihomo Party reports an unsupported format, ask the provider for a Mihomo-compatible subscription or check whether a format conversion option is required.
The profile loads with YAML or core errors
Read the first meaningful parser error in the log. It often identifies a line, an unknown field, a duplicate key, or an indentation problem. Remove tabs, check quotation marks, and confirm that the selected Mihomo core supports the fields used by the profile. Do not assume that every field from a different client or newer core is accepted by the installed version. If the profile came from a subscription, restore the provider’s original file or use a supported override instead of making repeated edits to generated content.
Every node fails
Compare the node test with the actual connection log. Confirm that the system clock is correct, because an incorrect time can break TLS certificate validation. Check whether the provider has imposed a traffic or device limit, whether the profile is outdated, and whether a local firewall is blocking Mihomo. If all nodes fail only for one destination, the issue may be destination-specific rather than a complete node failure. Test a known ordinary HTTPS site, then inspect DNS and rule matching.
The browser or application bypasses Mihomo
Confirm that the system proxy is enabled and that it points to the current local port. Disable browser proxy extensions and standalone VPN features during the test. Open a new domain and watch the connection log; reused browser connections may not create an obvious new entry. Applications that ignore system proxy settings require their own proxy configuration, environment variables, or TUN capture. If TUN is enabled, verify that it actually started and that the operating system granted the required permission.
The selected node is not used
In Rule mode, the selected node matters only when the matched proxy group uses that node. Inspect the rule result and group name in the connection details. A broad rule above the intended domain rule may send traffic to DIRECT, while a nested group may still point to another selector. For a controlled comparison, switch temporarily to Global mode, select the desired global group, and repeat the same test. Return to Rule mode after identifying the routing difference.
Use Mihomo Party reliably after the first setup
Once a profile and node work, keep the configuration easy to recover. Record the profile name, provider account, update interval, and any local override. Export manually maintained YAML files and save custom rule-provider files separately. Do not back up only the currently selected node: the group structure and rules determine how that node is used.
Refresh the subscription when nodes disappear, certificates change, or the provider announces an update. After every update, confirm that the expected group remains available and that the profile is still active. If Mihomo Party starts slowly or shows old data, check whether an older client process is still running, whether the local port is occupied, and whether the application has permission to write its profile directory.
- Keep one active proxy client at a time while testing system proxy behavior.
- Use Rule mode for normal split routing and Global mode only when you need a controlled comparison.
- Choose nodes using real service tests, not latency alone.
- Check the connection log before editing rules or changing DNS.
- Protect subscription URLs and rotate them if they have been exposed.
- Disable TUN before investigating a basic local-port or system-proxy problem.
The essential sequence is simple: add the subscription, update and activate the profile, select a node inside the group used by your rules, choose Rule mode, enable the system proxy, and verify the request in the connection log. Once each stage is confirmed independently, Mihomo Party becomes much easier to operate and future subscription or node failures can be isolated without repeatedly reinstalling the client.