This article addresses the common issue of “subscription links not updating.” Whether you use Clash, V2RayN, sing-box, or Shadowrocket, if a subscription refresh fails, shows a network error, or leaves you with no nodes after updating, follow the steps below to check your IP, DNS, browser environment, and client settings.
1. First, check whether the subscription link is accessible
Many update failures aren’t caused by a broken client. The subscription URL may be inaccessible, copied incorrectly, expired, or require a specific network environment. First, copy the subscription link into your browser’s address bar. If a block of configuration text downloads, the link is probably valid. If you see a 404 or 403 error, a blank page, or a timeout, continue troubleshooting.
- Check that the link is complete, especially that it starts with https://.
- Make sure you haven’t copied any extra spaces, line breaks, or non-English punctuation.
- If you’re using a free node subscription from this site, return to the latest page and copy the link again to avoid using an outdated URL.
- Try switching networks, such as switching between Wi-Fi and your phone’s hotspot.
2. How your IP and network environment affect subscription updates
Access to the subscription server may be unreliable due to regional network conditions, your ISP’s outbound routing, or frequent requests over a short period. First, try updating with your proxy turned off, then try again with it turned on to see which works. Some clients support updating subscriptions through a proxy. If a direct connection fails, enable this option in the settings. If the proxy itself isn’t working, turn it off and try again.
Clicking Update repeatedly may result in a temporary limit. Wait a few minutes before trying again, and avoid sending requests in quick succession. Company, campus, and public Wi-Fi networks may also block subscription URLs. In that case, testing with mobile data is usually the quickest way to check.
3. Incorrect DNS settings can also prevent updates
DNS translates a subscription domain name into an IP address. DNS poisoning, cache issues, or router hijacking can cause your client to connect to the wrong address. A common sign is that the subscription won’t open in your browser, but works on another network.
- On a computer, try changing your system DNS to 1.1.1.1, 8.8.8.8, or your ISP’s automatic DNS.
- In Clash-type clients, check whether the DNS module is misconfigured, and temporarily disable enhanced mode to test.
- On a phone, toggle Airplane Mode, or forget the current Wi-Fi network and reconnect.
- If you use a router, restart it to clear the old DNS cache.
After changing DNS settings, restart the client before updating. Don’t just refresh the interface.
4. Browser environment and client cache issues
Some subscription links contain a token, and browser extensions, ad blockers, private browsing, or system proxy settings may interfere with access. Try opening the link in a private window or using another browser. If the link opens in your browser but the client can’t update it, the issue is likely with the client cache, proxy mode, or subscription format recognition.
To fix this, delete the existing subscription and add it again. Avoid using special characters in the name. After pasting the link, save it first, then update it manually. Clash users should distinguish between a “subscription URL” and “importing a configuration file”—don’t treat a webpage URL as a configuration file. V2RayN users can select “Import subscription from clipboard” and then run “Update subscription.” sing-box users should make sure their client supports the subscription format.
5. Quick troubleshooting checklist
- Paste the subscription link into your browser and check whether it opens.
- Try updating with your proxy off, then test again with “Update through proxy” enabled.
- Switch between Wi-Fi, mobile data, and a hotspot to rule out issues with your current IP environment.
- Change your DNS and restart the client.
- Delete the old subscription and add the latest link again.
- Check the client logs, especially for messages such as timeout, 403, DNS failed, or format error.
If none of the above works, the subscription source is usually temporarily unavailable, the link has expired, or the format is incompatible with your client. Try another working subscription, or get the latest link from the free nodes page on this site and import it again. Keep this principle in mind while troubleshooting: verify the link first, then check the network, and finally address client cache and format issues. This is the most efficient approach.