This guide addresses the common issue of a subscription link failing to update. When clients such as Clash, V2RayN, or sing-box report an update failure, timeout, blank response, or inability to retrieve a subscription, the problem isn’t necessarily a faulty node. It may be related to your current IP network environment, DNS resolution, browser proxy settings, or the subscription link itself. Follow the troubleshooting steps below in order.
1. First, check whether the subscription link is accessible
If a subscription update fails, don’t rush to reinstall the client. Copy the subscription link and open it in a new browser tab. If you see a list of node configurations, base64 text, or a prompt to download a file, the link is probably working. If it won’t open in your browser either, the issue may be with the link, your network, or DNS.
- Check that the link is complete, including the
https://prefix and any parameters at the end. - Make sure the link hasn’t expired or been reset, and doesn’t require you to log in.
- If you’re using a free node subscription from this site, return to the original page and copy the latest link again.
- Don’t post your subscription link in public groups. Some services automatically invalidate links after detecting unusual access.
If your browser shows a 404 or 403 error, a certificate error, or a connection timeout, note the message—you may need it for the troubleshooting steps below.
2. IP environment: Your current network may not be able to reach the subscription source
Many subscription update failures are related to your current IP address or network. For example, company networks, campus networks, public Wi-Fi, or carrier networks may restrict access to certain domains or ports. Try switching networks: switch from Wi-Fi to a mobile hotspot, or from mobile data to broadband, then click “Update subscription” in the client.
If the update works on another network, the original network is likely preventing reliable access to the subscription source. In that case, enable the system proxy in your client before updating, or connect to a working node first and then update the subscription. Some clients offer options such as “Update subscriptions via proxy” or “Bypass mainland China addresses.” We recommend enabling Update subscriptions via proxy first, then trying again.
3. DNS: You’re online, but the subscription domain won’t resolve
A DNS issue may cause your browser to show messages such as “Server not found” or “DNS_PROBE_FINISHED.” The fix is straightforward: temporarily change your system DNS to a commonly used public DNS server, or enable the client’s built-in DNS. Windows users can change their IPv4 DNS settings in the network adapter properties; phone users can change DNS in the advanced settings for the current Wi-Fi network.
- After changing DNS, close and reopen the client.
- On Windows, run
ipconfig /flushdnsin Command Prompt to clear the cache. - If the link only fails to open in your browser, try another browser or an incognito window.
If the update still fails after changing DNS, paste the subscription link into the client again to avoid using a cached, outdated address.
4. Browser and client settings can also affect updates
Sometimes a subscription opens in the browser but fails to update in the client. Common causes include the client’s proxy mode, certificates, system time, or an outdated version. Try the following:
- Make sure your computer’s date, time, and time zone are correct. An incorrect time can cause HTTPS certificate validation to fail.
- Update clients such as Clash Verge, V2RayN, and sing-box to a recent stable version.
- Delete the old subscription configuration and add the link again instead of just clicking refresh.
- Close any other proxy software running on your system to prevent multiple proxies from competing for the same port.
- Check that the subscription type is supported. For example, don’t import a Clash subscription link into a client that only supports the v2ray format.
If the client reports a “parse error” or “yaml error,” the subscription content may be in an incompatible format. A “timeout” message is more likely to indicate a network or DNS issue.
5. Quickly identify the source of the problem
Use this rule of thumb: if the link won’t open in your browser, check the link, IP, and DNS first. If it opens in your browser but not in the client, check the client version, subscription format, and proxy update options. If switching networks fixes the update, the original network is likely restricted. If only one subscription fails, its source may be temporarily unavailable.
Finally, keep at least two working subscription sources and back up your current configuration before updating. If an update fails, don’t keep clicking refresh; wait a few minutes and try again. To troubleshoot a subscription link that won’t update, check link validity, IP reachability, DNS resolution, and client compatibility one by one. This is usually enough to identify the cause.