What should you do if your subscription link won’t update? This guide helps you distinguish an expired link from network connectivity issues, DNS resolution problems, and client format incompatibility. It applies to clients such as Clash, V2Ray, and sing-box. Keep your existing configuration, then test each possibility in order to avoid deleting nodes that still work.
1. Check the link and error message
- Open the “Subscriptions,” “Profiles,” or “Configuration” page in your client and try updating manually. Note the error message: timeouts, 403 or 404 errors, certificate errors, and resolution failures require different approaches.
- Copy the full subscription link again from your provider and check that it doesn’t contain extra spaces, line breaks, or Chinese punctuation. Don’t remove or change any tokens or parameters in the link.
- Make sure the link is compatible with your client. Clash configurations, universal node subscriptions, and sing-box configurations may not be interchangeable, so use the format explicitly recommended by your provider.
- Check the provider’s announcements to see whether the subscription has expired, been revoked, or moved to a new address. For free nodes on this site, refer to the latest instructions on the relevant page.
Subscription links often contain access credentials. Don’t share the full link in group chats, public screenshots, or with unfamiliar online conversion sites.
2. Check whether the issue is related to your IP address or network route
Some subscription links can be accessed directly, while others require a proxy. Providers may also restrict certain outgoing IP addresses or request rates. So even if a node connects, that doesn’t necessarily mean the subscription can be updated.
- Look in your client’s settings for options such as “Proxy for subscription updates” or “Download via proxy.” Some clients don’t offer this option; check their documentation.
- First try updating directly. If that fails, try again through a proxy you’ve confirmed is working. Don’t rely on a subscription that hasn’t downloaded successfully to establish a connection.
- Test once over Wi-Fi and once using your phone’s hotspot. If the update fails only on one network, check that network’s access restrictions or DNS settings first.
If you get a 403 or 429 error, stop retrying and check the provider’s restrictions. Changing your network route can help identify the cause, but it won’t necessarily bypass restrictions imposed by the provider.
3. How to test DNS and use a browser
If you see “Unable to resolve host” or “Server not found,” check whether your system can access other websites. Temporarily disable any custom Private DNS setting, or switch to a trusted DNS provider and try again. You can restore your original settings after testing. Don’t replace the subscription domain with an IP address, as this may cause certificate verification to fail.
Opening the subscription link in your browser can also help you troubleshoot: if a download starts or configuration text appears, your browser can retrieve the content on its current connection. A login page, CAPTCHA, or web error may indicate that additional verification is required. However, being able to open a link in your browser doesn’t mean your client can update it. They may use different proxy routes, DNS settings, cookies, and request methods. Incognito mode can help rule out some cookie or extension issues, but it won’t fix client format problems.
4. Run final checks based on the error
- Timeout or connection failure: Check that the update is using the correct network route, then test on another network.
- 404 or expired link: Get a new address from the provider’s page. Don’t guess at changes to the URL path.
- Certificate error: Check your device’s date and time zone, and update your operating system and client. Don’t disable certificate verification.
- Resolution failure or no nodes: Make sure the response isn’t a web page, and verify the subscription format. Back up your configuration before testing with an updated client from an official source.
If you still can’t update, contact your provider with your client name and version, the error message, and the networks you’ve tested. Hide your subscription token. Don’t start by uninstalling the software or clearing your configuration, as you could lose working nodes and rules.