When a subscription update fails, update only the affected group first and note the first specific error. Then check the URL, request route, DNS, and certificate, in that order. Set an auto-update interval only after a manual update succeeds and the group shows the expected nodes. This sequence also helps diagnose why manual updates work on Android but automatic ones do not.
Check the subscription URL and group first
A subscription update downloads a configuration list from a URL and adds recognized entries to a group. It does not test node connectivity or repair outdated nodes. A working old node does not mean the subscription URL is valid, and a successful update does not mean every node in the list is reachable.
- In v2rayN, open “Subscription Group” → “Subscription Group Settings,” find the group that failed, and check the “Optional address (Url)” field in its edit window. If the provider has reset the subscription, replace the address with the new one. Keep the full query string; don’t enter just the domain or edit the parameters yourself.
- Select the relevant group, then update the current subscription from the “Subscription Group” menu. Don’t update all groups at once, or successful results and errors from different groups may get mixed together. Don’t delete the group just to retry—you could lose old entries that still work.
- If the update reports success but no usable entries appear, make sure you’re viewing the right group and check that the response is a subscription format supported by the client. A login page, rate-limit message, or maintenance page can return HTTP
200without containing a configuration list.
Treat the subscription URL like an access credential. When contacting the provider, share the update time, domain, and status code. Before sending screenshots or logs, redact the full URL path, query parameters, and node credentials.
Compare results with and without the proxy
If the update request goes through the current node and that node is down, the client can’t use it to download replacement nodes. This means the update route depends on the existing configuration; it doesn’t mean the software is repeatedly sending the same request. Keep the subscription URL the same and change only the update method to see whether the route is the problem.
| Retry result | What to do next |
|---|---|
| Works without the proxy, fails with it | Keep the successful update result, then check the current node and core status. There’s no need to keep changing the subscription URL. |
| Fails without the proxy, works with it | At least one route can reach the subscription. Check DNS resolution and connectivity to the subscription domain on your current network; don’t assume one direct-connection timeout means the URL has expired. |
Both methods return the same 401 or 403 | Check the subscription credentials, permissions, or access restrictions imposed by the provider first. Switching nodes usually won’t fix a confirmed credential issue. |
In v2rayN’s “Subscription Group” menu, compare “Update current subscription (without proxy)” with “Update current subscription (through proxy).” The first option doesn’t actively use the client’s proxy, but traffic may still be routed through TUN, another VPN, or an upstream proxy. Change only one setting at a time, then restore the original settings when you’re done.
Use logs to tell DNS, certificate, and server errors apart
“Update failed” is just the result shown in the interface. Check the logs from the time of the update and look first for an entry with an exception, domain, or HTTP status code. These are common messages from the network stack and server; their exact wording may vary by system language and client version.
Error: No such host is known.
Cause: The DNS lookup route used for the request couldn’t resolve the subscription hostname. Try this: Check the domain spelling, run nslookup for it on Windows, and compare the result with one from another working network.
Error: The SSL connection could not be established, see inner exception.
Cause: The TLS handshake failed, but this message alone doesn’t tell you whether the issue is the certificate or another handshake problem. Try this: Check the system date and time first, then see whether the inner exception points to an expired certificate, a name mismatch, or a trust-chain issue. Don’t disable certificate validation.
Error: 401 Unauthorized
Cause: The server rejected the credentials sent with the request. Try this: Copy the full subscription URL again from your provider’s account page, replace the address in the group, and try a manual update.
Error: 429 Too Many Requests
Cause: The server is rate-limiting requests. Try this: Stop retrying repeatedly. Wait according to the response’s Retry-After value or the provider’s instructions, then increase the auto-update interval.
When running nslookup, enter only the hostname—not the protocol, path, or parameters. Resolving an address confirms only that this DNS lookup succeeded; it doesn’t prove that the client uses the same DNS route through a proxy or that an HTTPS connection can be established. If the log shows a connection timeout rather than a DNS error, use Test-NetConnection with the -Port 443 parameter in PowerShell to test TCP connectivity to the default HTTPS port. If the subscription URL specifies a different port, test that port instead. A successful TCP test doesn’t replace certificate and HTTP response checks.
Set auto-update intervals in v2rayN and v2rayNG
- v2rayN: Open “Subscription Group” → “Subscription Group Settings,” edit the group, enter an interval under “Auto-update interval (minutes),” and save. The interval is set per group;
0disables automatic updates for that group. The client’s built-in updater runs only while the program is running. It won’t continue in the background like a system scheduled task after the tray process exits. - v2rayNG: Open the top-left menu on the main screen, go to “Settings,” and look for the subscription auto-update option and interval. Manage group URLs under “Subscription Group Settings,” not in the node editor. The interface may vary by release, so use the units shown on your device. If there’s a toggle but no editable interval, don’t enter the desktop interval value into another field. Also make sure the target group is enabled, then verify manual refresh from “Update subscription” in the top-right menu.
- Check that it runs: Note the time and group of a manual update, then wait at least one full interval and check the logs or last-updated time. Don’t judge success by the node count: a successful update may leave the count unchanged if the server’s list hasn’t changed. Android background restrictions can delay updates, so the interval doesn’t guarantee execution at an exact time.
Choose an interval that matches how often the subscription changes
These are examples, not default values. For groups that change infrequently, start with once a day. If the provider specifies a minimum refresh interval, follow it. If manual updates still fail, fix the underlying issue first; shorter intervals will only mean more failed attempts.
Subscription update FAQs
Why does the URL open in a browser but fail in v2rayN?
The browser may use a different proxy, DNS route, or login session. First check whether it shows the subscription content or an account login page, then test the same URL in v2rayN using both update methods. A page that opens after you’ve logged in through a browser isn’t necessarily an importable subscription URL.
All my nodes disappeared after an update. Can I still troubleshoot?
Clear the list’s search filter and switch back to the group you just updated. If it has no entries, stop automatic updates and check whether the provider has stopped serving the configuration or switched to an incompatible format. If you have a valid backup saved locally, restore it.
Why don’t updates run on schedule when the Android screen is off, even though manual updates work?
First check the app’s auto-update option and the target group’s status. Then open v2rayNG’s app details in the system settings and check its battery or background activity restrictions. Change settings for this app only, and wait through a full interval to see what happens. Don’t disable power-saving features system-wide just to test.
One group keeps failing. Should I reinstall the client?
Check that group’s URL, credentials, and response format first. If other groups work on the same network with the same update method, focus on the failing subscription. Note the time and status code from one failed attempt and ask the subscription provider to investigate.