Importing a Clash Subscription Link: Format Detection, Update Failures, and Leak Response

Clash cannot import an arbitrary web address; it needs a Clash- or Mihomo-compatible subscription from the provider. When the client accesses the link, the server may return YAML with proxies, proxy-groups, and rules, or it may return encoded text, a sign-in page, or an error page. The response content determines whether parsing succeeds.

After pasting the link into the client, “added successfully” means only that the address was saved. It does not prove that the configuration downloaded or that its nodes work.

The token in a subscription address usually acts as a read credential. Troubleshooting requires only error status, response type, and time, not the complete URL. Hide everything after the question mark before sharing chat screenshots, recordings, or logs.

Some subscription services return different formats based on User-Agent. A browser displaying a string does not guarantee that a Clash request receives the same content; conversely, a web page in the browser does not necessarily mean the link is invalid. Give the provider the client version, update time, and status code instead of repeatedly deleting the configuration.

If the client offers direct link, configuration link, URL Scheme, and other entry points, start with an ordinary remote link. If one method reports client error(Connect), try another import entry documented by the client, but do not leave “allow invalid certificates” enabled.

Errors such as parse, yaml: unmarshal, or field not found mean the network request probably completed and the client failed while reading the content. Common causes include a server response formatted for another client, damaged YAML indentation, or fields unsupported by the current core.

Switching nodes usually does not help here. Preserve the first specific error line and line number, verify the client's Mihomo version, and ask the subscription provider for a compatible format. Do not manually repair dozens of fields in a remote configuration; the next update will overwrite every change.

If a remote update succeeds but the Proxies screen has no nodes, the response may contain only rules, every node may have been filtered out, or the selected configuration may still be the old one. Return to Profiles and check the selection marker, then confirm that the configuration contains proxies or proxy-providers and that proxy-groups references them.

Nodes can exist yet all sit in an unused group, leaving the primary policy on DIRECT. Choose a policy group that actually contains nodes and pin one, then observe a request in Connections. This reveals more about whether the configuration works than the latency button alone.

Clash normally continues using the last successfully downloaded local copy. Existing nodes may therefore keep working temporarily after a subscription expires or the server begins returning an error. Judge update status by the “last updated” time and the current error, not simply whether web pages open.

Do not rush to delete a working old configuration. Export the error, verify the account and link status, and remove the old entry only after the new address updates successfully. Deleting the sole working copy turns a diagnosable issue into an immediate outage.

Select the new Profile, pin one node in Proxies, keep Rule mode, and enable the system proxy. When visiting a familiar page, Connections should show the target domain, matched rule, and outbound route. A latency test proves only that the probe address responded; it does not replace a real request.

If a request enters Clash and shows timeout, try another node. If no record appears, inspect the system proxy. If it shows DIRECT, inspect the rule. Only when the page opens and the record matches the selection has the subscription completed downloading, parsing, activation, and forwarding.

Once a complete subscription appears in a public screenshot, group chat, support ticket, or unfamiliar conversion site, reset the subscription address in the service panel. After the new token works, replace the link in your clients and update. The old address should return an invalid status. Renaming the Profile does not invalidate the old credential.