This guide addresses a common issue: what to do when a subscription link won’t update. When clients such as Clash, V2RayN, or sing-box report an update failure or timeout, or download an empty configuration, the cause is often the current IP network, DNS resolution, browser settings, or system proxy environment. Follow these troubleshooting steps in order.
1. First, check whether the subscription link is accessible
Copy the subscription link, but don’t keep clicking Update in your client just yet. Open a browser and paste the link into the address bar. If it downloads a text file or prompts you to save a file, the link is probably working. If you see a 404 or 403 error, a certificate error, or a page that keeps loading, the issue may be with the link, network, or DNS resolution.
- Make sure you copied the entire link, especially the https:// at the beginning and any parameters at the end.
- If the link is from this site’s free nodes page, return to the original page and copy the latest subscription URL.
- Don’t share your subscription link in public chats or screenshots, as this could expose it.
If the link won’t open in your browser, your client won’t be able to update it either. In that case, check your network, IP, and DNS first rather than reinstalling the software.
2. Check your IP network: switch networks if a direct connection fails
Many subscription update failures happen because the connection between your current network and the subscription server is unstable. First, turn off your client’s proxy and try accessing the subscription over a regular connection. If that doesn’t work, try switching to a mobile hotspot, home Wi-Fi, or your workplace network. If the update works on a different network, the original network may be restricted or experiencing packet loss.
Recommended order: Disconnect your VPN or proxy, then update the subscription. If it still fails, switch networks. As a last resort, connect to a working node and try updating again. When a client is set to “Global Proxy” or “Rule-based Proxy,” subscription updates may use the proxy or connect directly, depending on the software’s settings.
3. DNS issues can also cause update failures
Your device must resolve the domain name before it can update a subscription link. If DNS is being tampered with, the cache is incorrect, or the response is too slow, you may see errors such as timeouts, connection resets, or “host not found.” Here’s what you can try:
- Restart your router and computer or phone to clear temporary network issues.
- Change your system DNS to a common public DNS server, such as 1.1.1.1, 8.8.8.8, or 223.5.5.5.
- On Windows, open Command Prompt and run ipconfig /flushdns to clear the DNS cache.
- Reopen your client and click “Update Subscription” manually.
Note: Avoid using multiple tools that manage DNS at the same time, such as security software, accelerators, and proxy clients. They can overwrite one another’s settings.
4. How your browser and system proxy settings can affect updates
Sometimes a subscription opens in your browser but won’t update in your client because they use different network settings. The browser may be using a system proxy, a proxy extension, or cached data, while the client connects directly when updating the subscription. Conversely, a browser extension may block the download, making the subscription appear unavailable.
Try these checks: open the subscription link in a private window; temporarily disable browser proxy extensions; check whether a leftover proxy setting from an old client is still enabled; and check your client’s settings to see whether subscription updates use a proxy. Clash-based clients usually let you change the update method in the configuration or proxy settings. In V2RayN, you can also try switching the system proxy setting before updating.
5. Practical steps to try in your client
If you’ve confirmed that the link works but the client still can’t update it, try the following:
- Delete the old subscription configuration and add the subscription link again instead of simply updating it.
- Check that your system clock is correct; an incorrect time can cause HTTPS certificate verification to fail.
- Upgrade to a recent stable version of the client. Older versions may not support some subscription formats.
- Check the logs for keywords such as timeout, DNS, certificate, or 403 to help identify the issue.
Don’t click Update repeatedly in quick succession. Too many requests in a short period may trigger a limit. Wait a few minutes before trying again.
Summary: Troubleshoot in this order: link, IP, DNS, proxy settings, client
If your subscription link won’t update, the most effective approach is to troubleshoot one layer at a time: first check whether the link opens in a browser, then test a different IP network, address any DNS issues, and finally check browser extensions, system proxy settings, and client configuration. For the free nodes on this site, use the latest information on the page. Copy the link and follow the steps above to import and update it, which should resolve most update failures.