Clash Subscription Not Working? Step-by-Step Checklist for Expired Links, Bad Formats, and Blocked Connections

Subscription Import Errors: First Identify Which Step Fails

When Clash Verge fails to import a subscription, the error falls into one of four stages: download failure, parse failure, YAML validation failure, or kernel load failure. Each stage has a completely different fix, so identifying the stage first saves a lot of time.

How to locate the issue: open the Subscriptions page in Clash Verge, click Update once, and watch when the error appears. If it fails before the progress bar finishes, it's a download problem. If it errors immediately after downloading, it's a parse or validation problem. If the config loads but the kernel fails to start, it's a field compatibility problem. The four sections below cover each case in order.

Link Reachability: Expired Links, Auth Failures, and Blocked Connections

Step 1: copy the full subscription link into your browser's address bar and open it directly. This gives you the fastest read on the problem:

• The response starts with proxies:: the link is fine, the problem is in the client
• A 404 or "link not found" page: the subscription has expired, regenerate it from your provider's dashboard
• A login page or plan-expired notice: your account is in an abnormal state, renew or reset the subscription first
• Infinite loading or timeout: the network path from your machine to the subscription server is broken

If the link opens in a browser but the client still fails to download, confirm with the command line. Open PowerShell on Windows or Terminal on macOS and run:

curl -v -L "subscription-link" -o sub.yaml -w "%{http_code}\n"

Pay attention to two parts of the output: the HTTP status code and the response body.

Some providers validate the User-Agent, and the client's default UA may be flagged as abnormal traffic. Clash Verge's subscription edit panel lets you set a custom User-Agent — just paste in a common browser UA string to get around it.

DNS pollution can also break subscription updates. When the subscription domain resolves to the wrong address, the browser may work fine because it goes through the system proxy, while the client's direct connection times out. Add the subscription domain to the direct-connection rules under Settings → Parameters → System Proxy, or temporarily switch to a working node before updating the subscription.

Response Format: HTML, Base64, and Converter JSON

If the link is reachable but the client still reports a parse failure, the response is usually not a standard YAML subscription. Open the link in a browser and check the beginning of the response:

• An HTML page: a provider announcement page, a Cloudflare challenge, or a 404 page — the link points to a web page, not a subscription
• Base64 gibberish: some providers encode subscriptions in Base64, which is normal
• A JSON structure: the provider has a subscription converter enabled, and this is the converted output
• An empty file: the server returned nothing, contact your provider

Clash Verge can import Base64 subscriptions directly and decodes them automatically. However, some providers mix line breaks or a BOM header into the Base64 content, which breaks decoding. Paste the link content into any Base64 decoder and confirm the decoded output starts with proxies: to rule out this class of problem.

If your provider gives you a subscription converter link, such as Subconverter format, it usually carries conversion parameters after the link:

?target=clash&url=original-subscription-link

Different converters use different parameter names, so it's best to use the dedicated "Clash subscription" link from your provider's dashboard instead of assembling parameters by hand.

There's one more hidden issue: some providers put the subscription content in HTTP response headers, or enable gzip compression without declaring Content-Encoding. Clients can't handle these anomalies automatically, so you'll need to contact provider support to fix them.

YAML Syntax Errors: Indentation, Quotes, and Full-Width Punctuation

The subscription downloads fine and is recognized as YAML, but the parser can't read it — the problem is YAML syntax. Provider-generated configs occasionally have errors, and users who hand-edit config files run into this more often. Common mistakes:

• Mixing spaces and tabs for indentation: YAML only accepts spaces; tabs cause an immediate error
• Missing space after a colon: name: NodeName is valid, name:NodeName fails to parse
• Unclosed quotes: node names containing special characters must be wrapped in quotes
• Full-width punctuation: full-width colons (：) and commas (，) mixed into the template are not recognized by the parser
• Unescaped # in URLs: # starts a comment in YAML, so any # inside a value must be wrapped in quotes

mihomo errors include a line number, for example:

yaml: line 12: mapping values are not allowed in this context

How to locate it: open Clash Verge's Settings → Parameters → Config Directory. The profiles folder contains the YAML file for your subscription. Jump to the reported line in a text editor and check the indentation, colons, and quotes.

Without a GUI, validate from the command line:

python -c "import yaml; yaml.safe_load(open('sub.yaml', encoding='utf-8'))"

Output of None means the syntax is valid; an error will point to the exact line and reason. Manual fixes are only temporary — the provider's next subscription update overwrites the whole file. The right move is to report it to your provider, or use a subscription converter to regenerate a clean config.

Kernel Field Compatibility: mihomo vs. Legacy Clash

If the subscription parses and loads but the kernel fails to start or some nodes are unavailable, it's a field compatibility issue. The Clash kernel has migrated from Clash Premium to mihomo, and the fields of the two generations are not fully interchangeable.

Outdated patterns commonly found in older subscriptions:

Fields newly added in mihomo are equally unrecognized by the legacy kernel, such as sniffer, profile.store-selected, and dns.fake-ip-filter.

How to tell: check the kernel log. Clash Verge's Settings → Parameters → Log shows kernel output; if you see unknown field or unsupported, the fields are incompatible. Fix priority:

1. Ask your provider for a mihomo-specific subscription link — most providers offer both Clash and mihomo links
2. Use a subscription converter to convert the old format to mihomo
3. Manually remove the incompatible fields in the subscription edit panel

When removing fields, don't touch the core fields in the proxies section. type, server, port, uuid, and alterId are the foundation of node connectivity; deleting the wrong one takes every node offline.

Full Checklist Order and Recovery Tips

String the four causes above into one path and work through it in order — most issues can be located within 5 minutes:

1. Open the subscription link in a browser and confirm the response is YAML or Base64
2. Use curl to check the HTTP status code; regenerate the link if you get 403 or 404
3. Save it as a local YAML file and validate the syntax with Python or an online tool
4. Check the kernel log and make sure there are no unknown field warnings
5. Delete the old subscription in Clash Verge and import the new link
6. Start the kernel and visit a site that requires a proxy to verify connectivity

If everything passes and it still doesn't work, send the subscription file and the kernel log to provider support along with your mihomo version number — that speeds up diagnosis considerably.

One last recovery tip: after each successful subscription import, copy a backup of the config file from the Subscriptions page. When a config goes wrong and you need to roll back, pasting the backup is much faster than troubleshooting from scratch.