This article addresses the common issue “What should I do if I can’t update my subscription link?” Whether you use Clash, V2RayN, sing-box, or another client, if refreshing the subscription fails, you see a network error, or no nodes appear after an update, follow the steps below to check your IP, DNS, browser environment, and client settings.
1. First, check whether the subscription link is accessible
A failed subscription update doesn’t necessarily mean the client is faulty. First, check whether the link opens normally. Copy the subscription link and paste it into your browser’s address bar. If the page displays a long list of node details or automatically downloads a file, the link is probably working. If you see a 404 or 403 error, a connection timeout, or a blank page, continue troubleshooting your network environment.
- Make sure you copied the entire link, especially the trailing parameters and symbols.
- Check whether the subscription has expired, been reset, or moved to a new address.
- If you got it from this site’s free nodes page, copy the latest subscription address and import it again.
- Don’t confuse a node-sharing link with a subscription link; they may have different formats.
If the link won’t open in your browser either, focus on checking your IP and DNS below. If it opens in the browser but won’t update in the client, check the client’s proxy mode and User-Agent settings.
2. What to do if your IP environment is preventing updates
Some subscription servers restrict suspicious access. Too many requests from the same IP, a data center IP, or an unstable proxy connection can all cause updates to fail. First, try turning off the client’s proxy and accessing the subscription over your local network. If that doesn’t work, try a mobile hotspot, home broadband, or another network.
Recommended order: try updating directly first, then try updating through a proxy. In Clash-based clients, you can temporarily disable the system proxy before refreshing the subscription. In V2RayN, exit the proxy or switch to “Clear system proxy” before clicking Update Subscription. If switching networks fixes the issue immediately, your original IP environment may be restricted or your route may be unstable.
3. DNS issues can also prevent subscription updates
DNS translates subscription domain names into IP addresses. If DNS is polluted, the cache is incorrect, or your carrier’s DNS is malfunctioning, the client may keep connecting to the wrong address. Try changing your DNS settings and updating the subscription again.
- Windows: Open your network adapter properties and change the DNS to a commonly used public DNS service.
- Phone: Change the DNS in your Wi-Fi settings or test using mobile data.
- Client: If supported, temporarily disable advanced features such as remote DNS, Fake-IP, and TUN mode before refreshing.
Restart the client after changing DNS settings. If necessary, restart your browser or computer too, so the old cache doesn’t remain in effect.
4. Check your browser environment and client settings
If the subscription opens in your browser but the client can’t update it, common causes include the client’s requests being blocked, subscription conversion failing, or traffic being routed through the wrong proxy rules. Try opening the subscription link in an incognito window and disabling ad blockers and privacy extensions so they don’t interfere with troubleshooting.
In the client, check for duplicate subscription group names, spaces in the link, and whether “Update subscription through proxy” is enabled. On some networks, enabling proxy-based updates causes them to fail; on others, updates only work through a proxy. Test both modes to quickly narrow down the problem.
5. Still can’t update?
As a last resort, follow this checklist: delete the old subscription and add it again; upgrade the client to the latest version; try a different network; paste the subscription into a browser to verify its contents; and check whether the error is a timeout, certificate error, or permissions error. If you see a certificate error, check that your system clock is correct. A permissions error or 403 may mean the subscription link has expired and needs to be retrieved again.
Don’t refresh repeatedly in quick succession. Too many requests in a short period may trigger restrictions. Change one variable at a time while troubleshooting—for example, change only the DNS or only the network—so it’s easier to identify the actual cause.