This article addresses the issue of subscription links failing to update. If Clash, V2Ray, sing-box, or another client reports an update failure, timeout, blank response, or 403/404 error, follow the steps below to check your network IP, DNS, browser environment, and client cache in order. This will help you quickly determine whether the link has expired, the network is blocking access, or there’s a local configuration problem.
1. First, check whether the subscription link is accessible
Many update failures aren’t caused by a broken client. The subscription address may have expired, been reset, or been copied incompletely. First, copy the link into your browser’s address bar and open it. Normally, you should see a block of node configuration text or an automatic download of a configuration file. If you see a not found or access denied message, or a blank page, the link may have expired and you’ll need to get a new one. This site also provides free nodes and subscription guides, but free resources can stop working at any time, so we recommend refreshing them regularly.
- Copy the entire subscription link, making sure not to omit the final characters.
- Don’t use the sharing page address in place of the subscription address; they’re usually different.
- If the link contains special characters, check that your messaging app hasn’t truncated it when you pasted it.
2. Check your IP environment: your current network may be restricted
If your browser can access other websites but the subscription link keeps timing out, the issue may be related to your current IP environment. For example, corporate networks, campus networks, and public Wi-Fi may block some remote configuration addresses. Some subscription services may also restrict frequent requests or access from certain regions. Try switching to mobile data, your home broadband, or another network.
Avoid clicking update repeatedly in a short period, as repeated requests may trigger security controls and temporarily block access. If you see a 403 or 429 error, wait a while before trying again on a different network.
3. DNS resolution errors can also cause update failures
Before a subscription can update, DNS must resolve its domain name to an IP address. If DNS is being interfered with, its cache contains incorrect information, or your ISP’s DNS is having issues, you may see errors such as “could not resolve host” or “connection failed.” Here are a few steps you can try:
- Restart your router and client to clear the old DNS cache.
- Change your system DNS to a commonly used public DNS server, such as 1.1.1.1 or 8.8.8.8.
- Turn off unnecessary proxy DNS testing options in your client, then try updating the subscription again.
After changing DNS, wait a few seconds before updating, or restart Clash, V2RayN, or your sing-box GUI client to apply the new settings.
4. Check your browser environment and client cache
If a subscription link opens in your browser but fails to update in the client, the issue is usually related to proxy mode, system time, or the cache. Make sure the client isn’t routing subscription update requests through an unavailable proxy. Try switching to direct mode and updating; if that doesn’t work, enable a working node and try again.
An incorrect system clock can also affect HTTPS connections, especially if your computer hasn’t synced its time for a long while. This can result in certificate errors. Enable automatic time synchronization and try again.
If you use Clash Verge, Clash Meta, V2RayN, or sing-box GUI, try deleting the old configuration and importing the subscription again instead of repeatedly overwriting the existing configuration. Be sure to back up any working nodes so you don’t delete them by mistake.
5. Recommended troubleshooting order
- Open the subscription link in a browser to check whether it’s still valid.
- Switch networks and test both Wi-Fi and mobile data.
- Change your DNS settings and restart the client.
- Check your system time, proxy mode, and client logs.
- Get a new subscription link and import it into the client.
In summary, subscription links that won’t update are usually caused by an expired link, an IP restriction, a DNS resolution issue, or a browser or client cache problem. Troubleshoot in this order: verify the link, switch networks, check DNS, and then reimport the subscription. This should help you identify the cause in most cases. If the update fails in multiple clients, the subscription source is the more likely culprit. If only one client fails, focus on its local configuration.