Subscription Update Failures: Timeouts, 403s and Parse Errors

Subscription errors look diverse but sort into exactly three bins: can't reach it, got rejected, can't read it. Find your bin and the fix follows.

1. Can't reach it: timeout / connection refused

The subscription server is unreachable from where you stand. In order:

1. Open the subscription URL in a browser. If a file downloads, the link is fine and the problem is app-side;
2. If the browser fails too, the subscription domain is likely blocked or poisoned. With any working node, use "Update via proxy" from the profile card's menu (or enable the proxy first, then update);
3. No working node at all? Update once over a phone hotspot, or ask your provider for a backup domain.

2. Rejected: 401 / 403 / 404

• 401/403 — token invalidated: quota exhausted, plan expired, or you reset the subscription in the dashboard. Copy the new URL from the provider and re-import;
• 404 — truncated copy-paste or the provider moved endpoints. Re-copy carefully, parameters included;
• 429 — rate-limited from updating too often. Wait a few minutes and raise the auto-update interval (1440 minutes is plenty).

3. Can't read it: YAML parse / missing fields

Download succeeded but the content isn't valid Clash config:

• The subscription is V2Ray/SS format, not Clash — find the Clash-specific link in the provider dashboard, see the import guide;
• unsupported proxy type — new protocol, old core: upgrade or switch to Alpha;
• Content starts with <!DOCTYPE — the server returned an HTML error page; treat it as a rejection (bin 2).