First, distinguish downloading, parsing, and activating a config

Importing a remote subscription involves fetching its contents, parsing the config, and activating it. These steps may appear in the same interface, but each can fail for different reasons. Note whether the error occurs when you click Import, manually update, or switch to the new config. In Clash Verge Rev, for example, you can manage configs from the Subscriptions sidebar and check Logs for errors from the core after switching configs. Button locations vary by version. If a download fails, keep the message shown on the subscription page too—the request may have failed before the contents reached the core.

Choose what to check based on the first specific error
Error or symptomCheck first
HTTP 401, 403, 404, or 410The server denied access or the path is unavailable. Check the subscription URL and account status.
no such host or lookup … timeoutDNS resolution for the subscription domain and the current network's DNS status.
certificate has expired or is not yet validThe device clock, certificate validity, and the domain mentioned in the error.
Messages such as yaml: line 12Check whether the response body is YAML, then inspect line 12 and the lines above it in a local copy.
Config imported, but activation reports a missing proxy groupRule targets, group names, and references in the merged config.

Subscription link expired, invalid, or returning a login page

  1. Check the service status on your provider's account page, then copy the subscription URL for the correct client again. Make sure it starts with the expected https:// and that you haven't copied any quotes, line breaks, or surrounding instructions. Don't remove query parameters manually.
  2. Check whether the provider recently reset your subscription token. Account validity and link validity are separate: an old link can stop working after a reset even if your account is active. Keep your working config, then update the URL or create a new entry as instructed by the provider and test it.
  3. Compare the service status with the HTTP response. 401 usually points to an authentication issue; 403 means the server refused the request, possibly due to an access policy. A 404 may simply mean the path is wrong. 429 indicates too many requests. If a Retry-After header is present, wait as instructed instead of repeatedly refreshing.

HTTP 200 only means a response was received. A login page, public Wi-Fi sign-in page, or server error message may also come back with 200. If your provider lets you save the response locally, open it in a text editor and check the beginning. If you see <!doctype html> or <html>, find out why you received a web page instead of changing the YAML. Your browser may send login cookies, but the client typically won't share that session—so a URL opening in your browser doesn't prove the subscription can be imported.

Network timeouts, DNS, and certificate errors

First, check whether the request can reach the subscription service

HTTPS URLs typically connect over TCP port 443 unless a port is explicitly specified. no such host indicates a failure during domain resolution. If dial tcp is followed by a connection timeout, check whether the log shows a destination IP. A standalone timeout doesn't tell you whether DNS, connection setup, or the server response was slow. Complete any sign-in required by the current network, then retry once on a trusted network you're authorized to use. Change only the network—not the URL and config at the same time.

If the log explicitly says it can't connect to a port on 127.0.0.1, compare that port with the listening port shown by your local client. Your system proxy may still point to a client that's no longer running, or subscription updates may be set to use a proxy that hasn't started. Note the original settings, restore normal internet access on the device, then retry. Enabling TUN won't fix an expired token or an invalid file format, so it shouldn't be the default first step when an import fails.

Check the device clock, then identify the certificate error

In Windows 11, open Settings → Time & language → Date & time. Check Set time automatically, then select Sync now. Also verify the displayed date and time zone. If the certificate still appears expired after syncing, ask the provider to confirm the certificate status for the subscription domain. For certificate signed by unknown authority, check the system trust chain or ask your administrator about certificate policies on managed networks. Don't disable certificate validation to import a subscription.

YAML parsing errors and format differences between Clash and mihomo

A subscription describes how content is delivered, not a fixed format. The same provider may offer Clash configs, mihomo-specific configs, or generic node lists. Text made up of individual node URIs—or an encoded node list—can't be imported directly as a complete Clash YAML config. A file containing only a proxies list may be intended for use with proxy-providers, rather than as a main config with proxy groups and rules. Choose an output format that matches your client and core.

  • Syntax errors: If you edited the config locally, check the indentation around the reported line and the section above it, list-item hyphens, and unclosed quotes. Use spaces for indentation. mapping values are not allowed in this context usually points to a structural issue, and the reported line may not be where the mistake begins.
  • Unsupported fields or protocols: Clash Meta continues development under the name mihomo. The original Clash and mihomo support different config features. For example, the original Clash doesn't support hysteria2 nodes. If a proxy type is unsupported, check which core and version are actually running—not just the client name. Don't rename the type to another protocol to get it past validation.
  • Reference errors: A config can parse successfully and still fail to activate. For example, the rule MATCH,手动选择 refers to a proxy group named 手动选择. If a merge or override renames or removes that group, the core may report it missing at load time. Check the final effective config, not just the remote source file.

Diagnose syntax in a local copy only if the original subscription is actually a config file. If the client supports importing local files, compare an unchanged copy: if it activates locally but fails remotely, focus on the download path and response differences; if both show the same syntax error, check the source file. Remote updates may overwrite local edits. After confirming a fix, report the issue to the provider or save any necessary changes in a separate client-supported override.

Update failed but the old config is still there: how to retest

If the old config still shows nodes, the client may be using the last saved version; that doesn't mean the latest update succeeded. Conversely, a newly activated config with no available nodes doesn't necessarily mean the subscription import failed. If the config fetches nodes separately through proxy-providers, the main config URL and provider URL are two independent requests. Check which request the log refers to before troubleshooting the main subscription or the provider.

  1. Keep your working config. Record the time of the attempt, client and core versions, the stage that failed, and the first specific error.
  2. Change one thing per attempt—for example, use a freshly copied link from your account page or correct the device clock. Then run one manual update and check for a new success entry.
  3. Make sure the updated config is the one that's active. Check whether the expected proxy groups and node sources have loaded; test node latency only after the config activates successfully. A latency timeout calls for checking the node or test target—it doesn't prove the subscription expired.

If you still can't pinpoint the issue, send the subscription provider or client maintainer a redacted report. Say whether the initial import or an update failed, whether it reproduces on another trusted network, and whether a local copy shows the same error. This narrows down the cause far better than simply saying “it won't import.”