This article addresses a common issue: what to do when a subscription link won’t update. You may have copied the subscription URL correctly, but clients such as Clash, V2Ray, and sing-box still report a timeout, an empty configuration, a download failure, or no change to the nodes after updating. Follow the steps below to troubleshoot IP, DNS, browser, and client settings.
1. First, check whether the subscription link is accessible
A failed subscription update doesn’t necessarily mean the client is broken. First, check whether the link opens normally. Paste it into your browser’s address bar. If you see a long string of configuration data, a downloaded file, or a prompt to download, the link is probably working. If you see a 404 or 403 error, a blank page, or a page that keeps loading, continue troubleshooting your network environment.
- Make sure the link doesn’t contain extra spaces, line breaks, or non-English punctuation.
- Check that the subscription hasn’t expired and that the provider hasn’t changed the URL.
- Try opening it in another browser, such as Chrome, Edge, or Firefox.
- If our free nodes page has a subscription link for today, try it to check whether your client is working properly.
Note: Don’t import an individual node link as a subscription link. A subscription is usually an HTTP or HTTPS URL that the client uses to retrieve multiple node configurations.
2. IP-related issues can prevent subscriptions from downloading
Some subscription URLs return different results depending on the IP address used to access them, or temporarily restrict requests that appear unusual. Updates may fail if your connection is being hijacked by your ISP, your company network imposes restrictions, or public Wi-Fi blocks the relevant domain. Try switching networks to check: turn off Wi-Fi on your phone and use mobile data to access the link, or connect your computer to your phone’s hotspot before updating.
If the update works on another network, the problem is probably with your original IP environment. Try restarting your modem and router to get a new IP address, or avoid restricted networks such as those at work or on campus. If your client supports “Use proxy to update subscription,” you can also connect to a working node first and then enable that option.
3. DNS and browser cache can also affect updates
DNS resolution issues are a common reason a subscription link won’t update. One sign is that your browser can’t open the subscription domain, even though other websites work normally. Temporarily change your system’s DNS to 1.1.1.1, 8.8.8.8, or a DNS server recommended by your ISP, then try opening the link again.
- Windows: Change the IPv4 DNS settings in your network adapter properties.
- macOS: Change the DNS settings in the network details under System Settings.
- Phone: Change the DNS settings in the advanced options for your current Wi-Fi network, or test using mobile data.
After making the change, it’s a good idea to clear your DNS cache. On Windows, run ipconfig /flushdns in Command Prompt. For your browser, turn off incognito or private browsing, clear the site cache, and make sure an old error result isn’t being reused. If the subscription won’t open in your browser, it generally won’t update in your client either.
4. Check client settings: Clash, V2Ray, and sing-box
Make sure the subscription URL is entered under “Subscription/Profile/Configuration file,” not in the manual node entry field. When updating, close any software that might conflict with the system proxy, and leave only one client running. In Clash-based clients, try deleting the existing configuration and adding the subscription again. In V2RayN, right-click the subscription group and select “Update subscription.” In sing-box graphical clients, check that the configuration source is enabled.
Common errors: A timeout usually points to a network or DNS issue. A 403 error may mean the link has expired or access is restricted. A YAML/JSON parsing error may mean the subscription content isn’t in a format supported by your client; try a compatible client or contact the subscription provider.
Finally, if the update succeeds but the nodes don’t change, the provider may not have updated them that day, or the client may be showing cached data. Close and reopen the client, then check the timestamp in the node list. Recommended troubleshooting order: check whether the link opens → switch to a different IP/network → change DNS → clear the cache → recreate the subscription. Following these steps will help you identify the cause of most subscription update failures.