This article 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, blank configuration, or unchanged subscription content, follow the steps below to check your network IP, DNS, browser environment, and client settings.
1. First, determine whether the problem is with the link or your local environment
A failed subscription update doesn’t necessarily mean the nodes are unavailable. Common causes include a mistyped subscription URL, a local network that can’t reach the subscription server, DNS resolution issues, or a client cache that hasn’t refreshed. Start with a simple test: paste the subscription link into your browser’s address bar. If it downloads configuration text or a file, the link is probably working. If the browser can’t open it either, continue by checking your network and DNS.
- Make sure the subscription link is complete and contains no extra spaces, line breaks, or Chinese punctuation.
- Check that the link starts with http or https and that you haven’t copied only part of the address.
- Try opening it over both mobile data and Wi-Fi to see whether your current network is blocking access.
- If the free node subscription on this site is temporarily unavailable, refresh the page later to get it again.
2. IP and network issues that can prevent updates
Some networks block or restrict access to subscription URLs, especially at workplaces, on campuses, or on public Wi-Fi. In these cases, the client may display messages such as “timeout,” “connection refused,” or “failed to fetch.” Try switching to a mobile hotspot. If the update works over the hotspot, the original network is likely restricting access.
Also note that when you update a subscription without connecting to a proxy, some clients use your local network directly. If that network can’t reach the subscription URL, the update will fail. In the client settings, look for options such as Use proxy to update subscriptions, system proxy, or TUN mode, and enable the appropriate option before trying again. If you’re using an old node to update the subscription, that node may have stopped working. In that case, import a working temporary node first, then refresh the subscription.
3. How DNS and your browser environment affect subscription updates
DNS translates domain names into IP addresses. If DNS is poisoned, has an incorrect cached result, or responds too slowly, the subscription link may not open. You don’t need to understand the technical details—just follow the steps below to change your DNS and clear the cache.
- On Windows, change your network DNS to 1.1.1.1 or 8.8.8.8, then reconnect to the network.
- On a phone, change the DNS in the settings for the current Wi-Fi network, or switch to mobile data to test.
- When opening the subscription in a browser, use a private window to avoid interference from extensions, cached data, or your login session.
- If the browser reports a certificate error, first check that your system clock is correct.
If the browser can open and download the subscription but the client can’t update it, check the client’s proxy mode, subscription group URL, UA settings, and whether security software is blocking it. Some security software may prevent Clash or V2RayN from accessing the network; temporarily allow the program to connect.
4. The correct update steps in your client
The basic troubleshooting process is similar across popular clients: remove the incorrect subscription, paste it again, update manually, and check the logs. Don’t click the update button repeatedly in quick succession. If an update fails, wait a few dozen seconds before trying again to avoid cache issues or too many requests.
- Copy the latest subscription link and make sure it contains no spaces.
- Open the subscription or configuration management page in the client.
- Delete the old subscription with the same name, then add the link again.
- Select Update via proxy or a similar option, then update manually.
- After the update completes, select a node, test its latency, and connect.
If the node list still shows old entries after updating, the client’s cache may not have refreshed. Exit and reopen the client, or clear the subscription cache before importing it again. For Clash-based clients, also make sure you’re using the new configuration file rather than an old Profile.
5. Key details to check if the update still fails
Checking the logs is more useful than reinstalling the client without a clear reason. Different log messages point to different causes: DNS usually indicates a resolution issue, timeout often means the network can’t reach the server, 403 may indicate access was denied, and 404 usually means the URL is wrong or the subscription has changed. In these cases, get the subscription URL again and test it on another network.
In summary, if your subscription link won’t update, first verify the link in a browser, then try another network and DNS, and finally check whether the client is using a proxy to update. Troubleshooting in this order usually helps pinpoint the issue and avoids repeatedly reinstalling the client.