On this page
The same private key decrypts your complete configuration, but an encrypted proxy provider still fails to update after you supply the key through global startup options. Keep the first error and your working configuration before generating new keys or deleting the subscription cache.
Confirm that the encrypted provider is failing
This applies to Mihomo proxy-provider data in age ASCII armor format: the running core has the matching global private key, but the entry's age-secret-key is absent or empty and it reports decrypt config error: no identities found. The message alone does not establish this bug.
Official issue #3449 compares global and provider private keys; the reporter used Alpha 478af2a. The version-pinned v1.19.33 implementation also shows the empty key being parsed first. This does not establish that all older versions or every subscription import failure are affected.
Identify the stage that failed
| What you see | Check first |
|---|---|
| An encrypted provider reports no identities found | Check the running core, global private key and the provider's own key setting |
| A login page, authentication failure or download timeout | Resolve content retrieval first; a decryption patch cannot fix that alone |
| The complete main configuration cannot be read | Check how the main configuration and private key are loaded; do not assume the provider issue applies |
Why is no identity found when a global key exists?
The provider parser passes the entry's age-secret-key to the decryption function. The old implementation tries to parse even an empty string as a private key. An error at that point prevents it from trying the global private keys. Leaving the entry without its own key can therefore block a working global key.
The #3450 fix skips genuinely empty strings so the existing global private-key logic can continue; it is included in the v1.19.34 stable release. It does not turn whitespace, damaged or invalid nonempty private keys into valid keys, or supply a global key to a process that has not loaded one.
For the standalone core, -age-secret-key defaults to the value of CLASH_AGE_SECRET_KEY. Setting a variable in your terminal does not mean an already running GUI client or background service inherited it. Check how the actual core is started, rather than a value in another terminal.
Update the running core, or specify the original key for the provider
Back up a recoverable configuration, your existing key-handling setup and the encrypted provider cache. Record the working core and startup method. Keep the ciphertext paired with its matching private key; do not generate an unrelated new private key for this error.
Obtain a core containing #3450 through a method supported by your project. The stable release verified here is v1.19.34. Client app users must check its supported core-update procedure: the app version alone is not enough, and executables in a service directory should not be overwritten arbitrarily.
Work with the same provider
Confirm that the original private key matches this ciphertext
Keep the existing valid private key and original provider content, and check your previous working records. The public-key recipient and private-key identity must match; a subscription token, public key or private key from another configuration is not a substitute.
Check the actual executable and updated core
For a standalone core, check the version of the executable actually in use. For a GUI client or service, inspect its core information and new startup log. Restart normally as that project requires, retaining the valid global private-key loading method so the new process actually uses the fix.
If you cannot update yet, use the provider's own field
Within the original proxy-providers entry, set age-secret-key to the same existing, matching, valid private key, then save and reload as before. The #3449 reporter observed successful decryption with this setting. This is a temporary workaround recommendation, not a device test performed by this site.
Keep other settings and refresh only this provider
Keep the original provider name, address, path and node selection, update the same provider again, and inspect the first error. Changing the subscription, changing keys or clearing the cache at the same time would remove the state needed for comparison and recovery.
mihomo -vThe command above identifies only the program it invokes; a same-named program in PATH may not be the core your client is running. The field below belongs inside the original provider entry and is not a complete configuration. Replace the placeholder with your existing matching private key; do not run it unchanged.
age-secret-key: "<YOUR_EXISTING_MATCHING_PRIVATE_KEY>"Keep the private key in a configuration location you control, away from support screenshots, command history and public logs. Do not edit regenerated runtime YAML to persist this field; use the existing supported configuration or persistent override entry point.
Verify the provider loads, then make a real request
Confirm that the newly started core contains the v1.19.34 fix, then update the provider that failed. Check that this update completes, the original decryption error disappears and the expected nodes actually load. An old list or a successful syntax check alone does not prove the remote ciphertext was decrypted.
Then select an expected node and make a fresh request to the intended destination, checking the connection record. Successful provider decryption only supplies node configuration; it does not guarantee that the node, DNS or destination service is reachable.
Verification checklist
- The running core, startup method and private-key source are clear; you have checked more than the GUI app version.
- You tested the same provider ciphertext and matching private key, without masking the result by switching subscriptions.
- This provider update succeeded, the expected nodes loaded and the original decryption error did not recur.
- Fresh proxy requests work; if they fail, keep the current first error to distinguish network problems.
- Your backup remains recoverable, and any extra provider private-key copy is covered by your configuration protections.
If it still fails, recover and follow the first error
The global private key never reached the service or client core
Check that project's supported startup configuration, restart normally and verify again. A temporary variable in another terminal does not prove an existing process received the private key.
The provider contains whitespace or an incorrect, damaged nonempty private key
Check the original valid private key against its ciphertext. The fix skips only empty strings; it does not silently ignore invalid keys or guarantee a successful fallback.
The content is not the expected age ASCII armor, or downloading already failed
Check the actual response content and download error, then confirm the format and key with the provider. The same patch does not explain a login page, an authentication failure or an unrelated YAML error.
Saving or reloading makes even the original configuration unusable
Stop making further changes and restore the verified working configuration, startup method and protected cache backup. If necessary, return to the previously working core through a supported method. Rolling back does not mean the old defect is fixed.
When reporting the problem, include the complete core version, provider type, whether keys are global or provider-specific, and the redacted first error. Keep the complete configuration, original ciphertext and private key under your control; remove subscription tokens, private keys and node passwords from support copies.
This article checks official releases, version-pinned source and issue discussions. We have not downloaded a core, processed your credentials or reproduced decryption in a real client. Issue #3449 remains open; a merged fix is not the same as issue closure or user acceptance.
References
- Mihomov1.19.34 stable release: the empty age private-key fix
- MihomoPR #3450: skip empty-string private keys during decryption
- MihomoIssue #3449: comparing global and provider private keys
- Mihomov1.19.34 decryption: provider and global private-key order
- Mihomov1.19.33 decryption: the previous empty-key handling path
- Mihomov1.19.34 provider parser: private-key field and decryption call
- Mihomov1.19.34 startup: global private-key argument and environment variable
- MihomoOfficial proxy-provider reference: age-secret-key and format requirements
