On this page
Confirm that the failure occurs after a successful download and the core rejects the configuration
This article covers a narrowly defined Clash Party 2.0 problem: the original Profile works, but refreshing a remote subscription causes configuration validation to fail, followed by failed hot reloads or core restarts. Official issue #2047 is not about a download timeout; the new file downloads and parses as YAML, but the final configuration fails Mihomo validation.
If the subscription address returns 401, 403, an HTML page, empty content, or Invalid YAML, the failure occurs earlier. Troubleshoot the subscription response and YAML syntax first. Continue with this article only when the download succeeds, the Profile is overwritten, and Mihomo then refuses to load it.
Branch from the last meaningful error
| Observed result | Failure stage | Starting point |
|---|---|---|
| 401, 403, timeout, or a returned webpage | The subscription request did not retrieve a configuration | Check the link, authorization, network, and provider status |
| Invalid YAML, indentation, or quote errors | The file has not passed YAML parsing | Fix the format without continuing to overwrite the current Profile |
| YAML is readable, but an error such as proxy group not found appears | Mihomo semantic validation fails | Check references among nodes, policy groups, rules, and overrides |
| The update succeeds, but only one node fails to connect | The configuration loaded; the problem is the node or protocol | Troubleshoot the node, TLS, UDP, or network |
If connectivity still works, preserve the currently running configuration first
After a configuration hot reload fails, the running Mihomo may temporarily continue using the previous working configuration. Do not rush to restart the core, quit the app, or refresh the subscription again. Those actions can discard the old working runtime state without fixing the new file already written to disk.
Stop clicking Refresh on the subscription card. If this Profile uses automatic updates, temporarily disable them and record the original interval. Then find the most recent working Profile in your backups or ask the subscription provider to fix the upstream configuration. Do not use your only backup as the test file.
Preserve the opportunity to recover
Hold the current runtime state
Do not switch Profile, restart the core, or relaunch Clash Party. First confirm whether a webpage still works through the original node.
Save the error and version information
Copy the validation error and record Clash Party, Mihomo, Profile, and the update time. Do not export a complete log containing secrets.
Copy the working backup
Copy the most recently verified Profile into a separate directory and leave the original untouched. If no backup exists, first ask the provider for a corrected configuration.
Stop overwriting
Until a candidate passes full validation, do not refresh manually or paste downloaded content back into the active Profile.
A file that opens as YAML is not necessarily runnable by Mihomo
A YAML parser verifies indentation, lists, and key-value structure; it does not prove that every policy-group reference exists. The example below is syntactically valid, but “Manual Selection” references an undefined policy group, so Mihomo still rejects it during loading.
Clash Party also combines the remote subscription with global overrides, per-Profile overrides, rules, and managed settings to produce the final runtime configuration. A remote file that looks valid alone can develop duplicate names, missing references, or unsupported fields after merging. Validate the final candidate instead of merely opening the YAML.
proxies:
- name: 节点 A
type: socks5
server: 127.0.0.1
port: 1080
proxy-groups:
- name: 手动选择
type: select
proxies:
- 不存在的策略组
rules:
- MATCH,手动选择The error says a proxy group does not exist
Check whether that exact name appears in proxies or proxy-groups, including spaces, capitalization, and full-width characters.
Validation passes after one override is disabled
The issue is in the merged result. Correct the stale group name or field in the override; do not change unrelated nodes.
The original subscription still fails when combined with every override
Give the provider the exact redacted error and ask them to fix the upstream generated configuration.
The same file passes with another core version
Keep both versions and the complete errors, then decide based on the Mihomo version you actually intend to run. A different core cannot substitute for acceptance testing.
Validate the new subscription separately as a candidate file
Save the new subscription as a temporary copy first. Do not overwrite the current Profile or submit a token-bearing link to an online converter. Verify that every rule target, policy-group member, and override reference exists, then test the final candidate with the Mihomo core actually selected in Clash Party.
Command-line users can run Mihomo test mode against the temporary copy. A successful exit means only that this core can parse and initialize the candidate; it does not prove that nodes connect or replace the real-request test that follows. Never rewrite the only original configuration in place.
From candidate file to importable configuration
Keep the original remote response
Place this download in a temporary directory and save a separate redacted copy for comparison. Do not put the subscription URL in shell history or a support ticket.
Verify references
Start with the group named in the validation error. Inspect proxies, proxy-groups, rules, and rule-providers, then fix any target that is missing or renamed.
Apply the actual overrides
Include global overrides and this Profile's overrides in the check. If only the merged result fails, fix the override instead of repeatedly downloading the same subscription.
Test with the selected core
Run test mode on the temporary final configuration and save the exit code and error. Proceed to import only after a successful exit.
mihomo -t -f candidate.yaml- Remote subscription candidateWrite only to a temporary file; do not overwrite the current Profile
- Merge rules and overridesGenerate the final configuration Clash Party will actually run
- Selected Mihomo -tCheck group references, fields, and core compatibility
- Save only after successOn failure, clean up the temporary file and preserve the previous working configuration
PR #2048 moves saving until after Mihomo validation. v2.0.0 does not include this protection; v2.0.1 officially does. Upgrading does not automatically restore a Profile that was previously overwritten.
If the app no longer starts, restore the previous working Profile
If the core has stopped, disable the system proxy and TUN first and confirm that the operating system can connect directly, so downloads do not keep pointing to an inactive local port. Then import the backed-up working configuration as a new Profile. Keep the damaged Profile only for offline comparison and do not make it current again.
If you have no backup, do not gamble by deleting the entire Clash Party data directory. Ask the subscription provider to correct the configuration, perform semantic validation in a temporary location, and import it under a new name. This preserves the existing overrides, error evidence, and rollback clues.
Recover in rollback-safe order
Restore direct system connectivity
Disable the system proxy and TUN, and confirm that the browser no longer connects to an inactive local proxy port. Record the original settings so you can restore them one at a time.
Import the previous working copy
Create a Profile under a new name. Do not delete the failed configuration or enable automatic updates yet.
Start the core and test one node
Select a known working node, open an ordinary webpage, and confirm in connection records that the request actually entered the new Profile.
Restore automatic updates last
Restore the original update interval only after a manual update, reload, and app restart all succeed once.
v2.0.1 officially includes validation before saving
Clash Party v2.0.1 was released on 8/11/2026. Its official release notes explicitly fix remote subscription updates that failed to validate the configuration before overwriting a working subscription. v2.0.0 still lacks this protection; the current stable release is v2.0.2. Users on an older release should back up the working Profile, then upgrade from the official Release.
v2.0.1 treats the remote subscription as a candidate, applies managed settings, rules, and overrides, then validates the temporary file with -t mode from the selected Mihomo. If validation fails, it neither replaces the saved Profile nor reloads the core, and then removes the temporary file. This protection applies only to future updates; it cannot recover an old configuration overwritten before the upgrade.
Available options
| Option | Who it suits | Constraints |
|---|---|---|
| Upgrade to v2.0.1 or a newer stable release | Users who want validation before updates | The current stable release is v2.0.2. Back up the Profile first, then use an invalid candidate to confirm that the old configuration is not overwritten. |
| Temporarily stay on v2.0.0 | Users who cannot schedule an upgrade yet | Pause automatic updates and validate candidates manually; the older release can still overwrite a working Profile |
| Downgrade the app | Only for another clearly identified release regression | It cannot restore an overwritten Profile or guarantee avoiding the same update path |
Complete acceptance testing with both an invalid and a valid candidate
After upgrading to v2.0.1 or a newer stable release (currently v2.0.2), run two updates in a backed-up environment. First use a redacted invalid candidate and confirm that Clash Party returns a validation error while the old Profile contents, current core runtime, and node connection remain unchanged. Then use a verified valid candidate and confirm that saving, reloading, and real browsing all succeed.
An “update complete” message alone is not enough. Full validation means an invalid update cannot damage the previous working configuration, a valid update takes effect, and after quitting and restarting Clash Party you can still select policy groups, produce connection records, and disable and restore the system proxy or TUN normally.
v2.0.1 update-protection checklist
- Clash Party has been upgraded to the official v2.0.1 or a later stable release that explicitly includes this fix
- An invalid candidate displays the specific Mihomo validation error
- An invalid candidate does not overwrite the previously saved working Profile
- When validation fails, the current Mihomo is not reloaded or stopped
- A valid candidate can be saved, with the expected nodes and policy groups visible
- A real webpage request appears in connection records with the expected rule and egress
- Connectivity still works after quitting and reopening the app, and the system proxy and TUN can be restored normally
- A new working backup is saved before automatic updates are reenabled