This guide explains what to do when a subscription link won’t update. If clients such as Clash, V2RayN, or sing-box report an update failure, timeout, parsing error, or an empty import, the nodes may not actually be unavailable. The issue could also be related to your current IP, DNS, browser environment, or how you’re accessing the subscription URL. Follow these steps in order to troubleshoot.
1. Check whether the subscription link is accessible
Copy the subscription link, but don’t keep retrying the update in your client just yet. Open a private browser window and paste the link there. If you see a long string of configuration data, Base64 text, or an automatically downloaded file, the link is probably working. If you get a 404 or 403 error, or the connection times out, continue troubleshooting your network environment.
- Make sure you copied the entire link, especially the token, parameters, and equals sign at the end.
- Don’t use a webpage URL as a subscription link. A subscription link is usually a URL that returns configuration data directly.
- If the free nodes page on this site offers multiple subscription links, try a different one.
Note: A failed subscription update doesn’t mean all your nodes are unusable. First determine whether the subscription can’t be retrieved or the nodes themselves can’t connect.
2. Check your IP environment: switching networks is more effective than repeatedly refreshing
Some subscription services restrict unusual access patterns, frequent requests, or traffic from certain network gateways. If an update fails on a company or campus network, or public Wi-Fi, try switching to your phone’s hotspot. If the update works over mobile data but not on your original network, the issue is likely with your current IP address or network policy.
- Turn off your client’s proxy and access the subscription link over a direct connection.
- Switch to mobile data or another Wi-Fi network, then update the subscription again.
- Wait a few minutes before trying again to avoid triggering restrictions with repeated requests.
- If your client supports updating subscriptions through a proxy, test with the option both enabled and disabled.
Tip: Keep your network setup simple while updating. Don’t run multiple proxies, accelerators, or browser extensions at the same time.
3. DNS resolution issues can also cause update failures
If your client reports “host not found,” “lookup failed,” or “DNS error,” check your DNS settings. You can temporarily change the DNS server in your system’s network settings to a common public DNS server, such as 223.5.5.5, 119.29.29.29, 1.1.1.1, or 8.8.8.8, then disconnect and reconnect to the network. On Windows, you can also open Command Prompt and run ipconfig /flushdns to clear the cache.
If the update fails only in your client, but the subscription link opens in your browser, the client’s DNS settings or proxy mode may be affecting the request. Try restarting the client, switching between Global, Rule, and Direct modes, or deleting and re-adding the subscription.
4. Common browser and client issues
Even if a link opens in your browser, that doesn’t guarantee it will work when pasted into a client. The browser may have automatically encoded the link, or your copy may include spaces or line breaks. Use “Copy link address” instead of copying incomplete text from a redirect. If the link contains characters such as &, ?, or %, make sure to preserve them exactly.
- Clash clients: Check whether the configuration file is read-only, and avoid special characters in the subscription name.
- V2RayN: Right-click the subscription group and select Update current subscription. If that fails, try deleting the group and setting it up again.
- sing-box clients: Make sure the import type is set to subscription/remote configuration, not local JSON.
Recommended troubleshooting order: Test the link first, then switch networks, change DNS, and finally reinstall or switch clients. Don’t clear all your settings right away, or you may lose nodes that were working.
5. Still can’t update?
If the subscription won’t update on multiple networks, with multiple DNS servers, and in multiple clients, the subscription source may be temporarily unavailable, the link may have expired, or access permissions may have changed. Try again later or use a new subscription link. When importing free nodes from this site, save your existing configuration first so you can restore it if needed.
Summary: When a subscription link won’t update, the key is to identify whether the issue lies with the link itself, your IP or network, DNS resolution, or the client environment. Follow the steps above in order to pinpoint the problem quickly.