Subscriptions and Configuration Import FAQ
Troubleshoot Clash subscription imports, failed updates, empty nodes or groups, YAML errors, incompatible formats, and token safety with symptom-based checks.
Start with what happened during import
Use the response, status code, and log message to distinguish link, format, authentication, and client compatibility problems.
What If a Subscription URL Fails to Import or Update?Common causes include an expired URL, an invalid token, network access failure, TLS verification failure, an unsupported response format, or server-side rate limiting.What If Import Succeeds but No Nodes or Policy Groups Appear?A successful import only means the client read the response. Confirm that the configuration contains proxies, proxy-groups, and rules and that its format is compatible with the active core.How Do I Fix YAML Parsing, Indentation, or Unsupported-Field Errors?Clash uses YAML, so indentation, colon, quote, or list errors can prevent loading. Follow the log's line and column, then confirm the field is supported by your core version.What If the Subscription Format Is Incompatible with the Client or Core?A subscription URL may return Clash, Mihomo, or Clash Meta configuration, generic proxy links, or a rule set. Clients and cores do not all recognize the same formats.