Node HandbookNODE HANDBOOK中文
Clash Verge Rev · subscription import

the remote profile data is invalid yaml in Clash Verge Rev

This string is often read as "the subscription expired". In the client's own code it marks one specific branch: the HTTP request succeeded, and the response body did not parse as the YAML mapping the client expects.

Node Handbook editorial team ·

Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.

Which step the error points to

In the published parsing code for remote profiles (commit 603e616 at the time of checking), Clash Verge Rev does three things in this order: it checks the HTTP status of the remote request, it decodes the response body as a YAML mapping, and — only after that succeeds — it checks whether the top level contains proxies or proxy-providers.

So the remote profile data is invalid yaml means: the body fetched in this attempt did not match what the parser expected. It does not, by itself, tell you that the subscription has expired, that all nodes are dead, or which line is wrong. Code branches move between releases, so this commit describes behaviour at that point, not every historical version.

Match your evidence to the branch

Evidence you haveMost likely branchWhat to do next
failed to fetch remote profile with status ...The HTTP response failed before parsingWork from the status code and the access conditions; YAML fixes do not apply
the remote profile data is invalid yamlBody reached the parser and did not matchCheck the type and structure of what the URL actually returned
Error says proxies or proxy-providers is missingYAML parsed, but a required top-level key is absentConfirm you are not importing a different subscription format
Import succeeds but the node list is emptyParsing already passedCheck proxies, proxy-providers, the active profile and proxy-group references

These four outcomes come from adjacent branches of the same code path. They are not interchangeable descriptions of one symptom.

Troubleshoot in order

  1. Keep the working profile. Note the Clash Verge Rev version, the OS, the time of failure and the full error text. Do not delete a profile that still works. Redact the subscription URL, tokens, node addresses and account details before sharing a screenshot.
  2. Confirm the subscription type. In the provider's own dashboard, check that you copied the link intended for Clash/Mihomo. The fact that the same link imports in another client does not prove it is Clash YAML.
  3. Look at what this response actually is. Only on your own trusted machine, check whether the URL returns a configuration, a login page, a verification page, an error page, or nothing at all. Do not paste a token-bearing URL into an online YAML validator, and do not post the full response body to a forum. If it returns HTML or an access restriction, fix the link and authentication in the provider dashboard. If it returns a different subscription format, use the Clash/Mihomo-specific endpoint the provider offers.
  4. If it is YAML, check the structure. After backing up locally, check indentation, colons and quoting, and confirm the top level contains proxies or proxy-providers — the Mihomo configuration reference documents both as configuration keys. A .yaml extension does not guarantee the body is valid YAML, and a file that contains private keys should not be handed to a third-party parsing site.
  5. Change one variable. If the provider offers several formats, switch only to the one labelled Clash/Mihomo and import once. If there is only one link, ask the provider to confirm what format it actually returns. Do not clear the cache, reinstall, change the core and change the subscription in the same attempt — afterwards you will not know which step mattered.
  6. Accept the fix from a new log. Once the error is gone, confirm the active profile switched, that nodes or providers loaded, and that the core starts without a new error. A silent import is not proof that the profile is usable.

Two easy misreads

Base64 that looks like YAML trouble. Issue #2374 records a macOS user whose subscription returned Base64 content; another client accepted it while Clash Verge Rev reported a YAML error. That supports the step "check what format the source returns". It does not prove every occurrence of this error is Base64.

Advice from comment threads. Issue #471 records the same error string with a description too thin to yield a general root cause. Do not copy the unreproduced suggestions in that thread — clearing caches, skipping certificate verification, or reinstalling — as if they were a fix.

If the message becomes a missing proxies or proxy-providers warning, you have moved from "cannot parse" to "parsed but incomplete". If the update succeeds but the proxy page stays empty, check provider fetching and the use references in proxy groups. Neither of those is still an "invalid yaml" problem.

Sources and scope

Based on the Clash Verge Rev remote-profile parsing code checked on 2026-11-07 (commit 603e616), the Mihomo configuration reference, and public issues #2374 and #471. Public issues are individual reproduction records. This page was not reproduced across every OS, client version and provider, and it cannot see your private subscription response.

Frequently asked questions

The same link works in Shadowrocket. Why does Clash Verge Rev fail?

Different clients accept different subscription formats. Confirm that the response is Clash/Mihomo YAML and ask the provider for the matching endpoint. A second client importing it does not prove the response suits Clash Verge Rev.

Does invalid yaml mean the subscription expired?

No. Expiry, a login page, a verification page, an error page and a genuine YAML syntax error all have to be checked separately, both in the returned body and in the provider dashboard.

The file is named .yaml, so why does it still fail?

The extension does not guarantee the body is valid YAML. The actual content may be HTML, Base64, truncated text, or YAML with a syntax error.

Can I paste the subscription into an online validator?

Not advisable. Subscriptions usually embed access credentials. Check on your own device, and send the provider only redacted status, size and format information.

The error is gone after updating, but there are no nodes. What now?

Parsing has passed. Check the active profile, the contents of proxies or proxy-providers, provider fetching, and proxy-group references. That is a different failure stage.

Would disabling certificate verification fix it?

This error gives no evidence that TLS is the problem. Do not turn off certificate checks to work around a format error. Check the request status and the body format first.

Continue reading

set system dns failed: exit code 1 · config.yaml is empty in FlClash · Full error string index