This article addresses the problem of what to do when a subscription link won’t update when multiple team members use clients such as Clash, V2RayN, and sing-box. Common symptoms include one person being able to update while others cannot, the same link behaving differently on different computers, or an empty node list after an update. Follow the steps below to quickly determine whether the cause is the client, network environment, link permissions, or account environment stability.
1. First determine whether the link has expired or the update is failing on your device
When using subscriptions as a team, don’t immediately reinstall the client. Start with a cross-test: try the same subscription link on two devices and two networks, such as your company Wi-Fi and a mobile hotspot. If everyone is unable to update, the subscription address itself, server access restrictions, or an expired link are the most likely causes. If only some people are affected, focus on the local proxy, DNS, system time, and client cache.
- Copy the subscription link and make sure it contains no extra spaces, line breaks, or Chinese punctuation.
- Open the link in a browser. If it downloads text or configuration content, the link is generally accessible.
- Switch to a mobile hotspot and try again to rule out company network restrictions or DNS interference.
- Ask another team member to import the link using the same client to determine whether the issue is related to the account or device environment.
If the browser shows a 403 or 404 error, times out, or asks you to log in, the client won’t be able to update either. Don’t keep retrying—instead, first confirm that the link is still valid. We also recommend regularly copying the latest address for the free node subscriptions provided on this site to avoid using an outdated cached link.
2. Can team account environment stability affect updates?
Yes. Teams often share the same subscription link, but different clients may request updates at different times, from different IP addresses, and with different UAs. If the subscription source has limits based on request frequency, device count, region, or login status, some users may be able to update while others cannot. Multiple people clicking Update at the same time may trigger temporary rate limiting, resulting in update timeouts, blank configurations, or a “Unable to retrieve subscription” message.
For team use, it’s best to assign one administrator to manage the subscription source and have other members import it using the same steps. Avoid repeatedly sharing links in chat that have been shortened or rewritten by link previews. If the subscription requires account authorization, switching devices, incorrect system time, or leaving an old proxy running for a long time can also make the request environment unstable.
3. Practical troubleshooting steps in the client
- Clash Verge / Clash Meta: Go to “Subscriptions/Profiles” and try updating. If it fails, delete the old configuration and paste in the original subscription link again. Also check whether an old configuration has taken control of the system proxy.
- V2RayN: Edit the address under “Subscription Group” and make sure the URL is complete. Try both “Update subscription without proxy” and “Update through proxy.”
- sing-box clients: Confirm that the configuration source supports the current format. If the import is empty, the subscription format may be incompatible; try a link in Clash or V2Ray format instead.
- Windows users can try closing and reopening the client. macOS users should check that the app has network access permission. On mobile, try switching between Wi-Fi and cellular data.
Also check that your system time is correct. A significant time discrepancy can cause HTTPS certificate verification to fail, preventing the subscription from being fetched. You can temporarily switch to a public DNS server or toggle between “Update directly” and “Update through proxy” in the client.
4. How to prevent update problems from recurring across the team
For team use, create a simple guide that explains who maintains the subscription link, how often it’s updated, which client versions are supported, and who to contact if an update fails. Don’t manually copy individual nodes to team members; use a subscription to keep everyone in sync. For members who travel frequently or use networks with complex restrictions, prepare a backup subscription or client so that a problem with one tool doesn’t disrupt all connections.
In summary, if you’re wondering what to do when a subscription link won’t update, first cross-test whether the link is accessible, then check client settings and the network environment, and finally check whether the team account has limits on request frequency, devices, or permissions. Troubleshooting in this order—link, network, client, account environment—is the most efficient approach.