For users whose subscriptions won't refresh, whose server list is empty after an update, or who want to schedule updates. First distinguish request failures from parsing errors, then decide whether to fetch through a proxy. Before enabling auto-updates, check that the client offers the option, confirm the interval unit, and make sure background tasks can run. A shorter interval won't fix a broken connection.
Subscription updates and node connections are different
A v2rayNG subscription update sends a request to the subscription URL, reads the server's response, and adds compatible node configurations to the relevant group. Node connections, by contrast, are established by the Xray core using the selected configuration. The two may use different addresses, authentication, and network routes. So a working node doesn't prove the subscription endpoint is accessible, and a successful subscription update doesn't mean every node will connect.
Keep your working configuration while troubleshooting; don't delete the entire subscription group just to refresh the list. Note where the failure occurs: a request that keeps waiting usually points to a network issue; a clear HTTP status points to the endpoint or account; only when the request finishes but no nodes appear should you investigate the response format and protocol compatibility. This order helps avoid mistaking a network problem for a core issue.
- Request doesn't complete: Check DNS resolution for the subscription domain, your current network, and both direct and proxied access.
- Request is rejected: Check your account's expiration, subscription token, API rate limits, and server-side access restrictions.
- Content can't be imported: Check that the response contains a node subscription, not a login page, error page, or another configuration format.
Common subscription update errors and how to troubleshoot them
Open the v2rayNG menu and check the “Logs” after trying a manual update. Look for errors from the same time; exact messages vary across builds and network stacks, and some update errors appear only in a notification. Before sharing logs, redact tokens in subscription URLs, account identifiers, and node credentials.
Error: Unable to resolve host
Cause and fix: The subscription domain couldn't be resolved. First check that the domain is complete, then compare Wi-Fi and mobile data. If only updates through a proxy fail, also check whether the DNS used by the proxy connection is working.
Error: connect timed out
Cause and fix: A connection wasn't established before the timeout. Confirm that your current network can reach other websites, then compare direct updates with updates through a proxy. Avoid repeated taps that pile up failed requests.
Error: HTTP 403
Cause and fix: The server rejected the request. Check whether the subscription was reset, the account is restricted, or the server limits access by source. Switching nodes may not resolve an authorization issue.
Error: HTTP 429
Cause and fix: The endpoint is rate-limiting requests. Stop refreshing repeatedly. If the response includes Retry-After, wait for the specified time, and check whether multiple devices are updating too frequently.
Error: SSLHandshakeException
Cause and fix: The TLS handshake failed. Check your system date and time and whether you need to sign in to the network, then verify the server certificate. Don't bypass subscription endpoint errors by disabling certificate validation.
If none of these errors appears and the app only says the import failed, copy the full subscription URL again, including all parameters after the question mark. Don't use a management panel URL as the subscription URL, and don't decode it, remove percent-encoding, or truncate the end. HTTP 200 only means the request succeeded at the HTTP level; the response could still be a login page. Ask your subscription provider which format works with your client.
When to turn on “Update through proxy”
The difference between a regular update and an update through a proxy is whether the subscription request uses the proxy route provided by the client. In v2rayNG, these options are usually in the top-right menu on the main screen, with labels such as “Update subscription” and “Update subscription (through proxy).” Labels and scope can vary by build, so check whether the action applies to the current group or all subscriptions. Proxy updates require an already working proxy connection; they can't revive a configuration where every node is down.
| Current situation | Try first | Check |
|---|---|---|
| Endpoint works directly | Regular update | Less reliance on the current node |
| Direct connection times out; a working node is available | Update through proxy | Start the connection and verify access first |
| None of the existing nodes work | Switch networks, then try a regular update | Ask the provider for a working subscription or backup configuration |
| Endpoint returns 403 or 429 | Resolve the access issue or rate limit first | Don't use repeated exit-node switching as a substitute for troubleshooting |
Bottom line: verify the proxy before using it to update subscriptions
Select a working node and start the connection first. Once you've confirmed that access works, try updating through the proxy. If only proxy updates fail while regular updates work, prioritize restoring regular updates; there's no need to change the protocol, DNS, and routing rules all at once.
A “connected” icon doesn't prove the remote service is reachable, and a latency test alone can't cover every access scenario. Some subscription endpoints restrict access based on the source network, so a proxy exit may actually be blocked. When comparing methods, change only one condition at a time and record the update method and error so you can pinpoint what changed.
v2rayNG auto-update intervals: check your build's settings first
Subscription management varies across v2rayNG builds, so don't apply v2rayN's menu path to Android. Open “Subscription group settings,” edit the relevant group, and check whether it actually has an auto-update toggle and interval field. If not, check subscription-related options under “Settings.” If there's no such field, don't assume a hidden scheduled task exists, and don't mistake Android's “auto-sync” setting for a subscription update toggle.
-
Check the subscription group
Open “Subscription group settings” from the side menu, edit the target group, verify the URL, and save. Try a successful manual update first to rule out issues with the URL itself.
-
Check for update options
Look for auto-update fields in the group editor and under “Settings.” If an option is available, follow the field instructions. If not, update manually rather than relying on screenshots from another client.
-
Check the interval unit
Use the unit shown in the interface—minutes or hours. For example, to update every 6 hours, enter 360 in a minutes field or 6 in an hours field. These are examples, not defaults for every build.
-
Check background restrictions
On Android, go to “Settings” → “Apps” → “v2rayNG” and check battery and background data restrictions. Menu names vary by device. Allow background activity if needed, then monitor whether updates actually run.
Even if your build supports scheduled updates, sleep mode, unavailable networks, and force-stopped apps can delay tasks. Allowing background activity only rules out system restrictions; it won't add scheduling to a version that lacks it. If your current interface has no confirmed auto-update option, the reliable approach is to refresh manually before use and update promptly when your subscription provider announces configuration changes.
v2rayN auto-update intervals: how desktop differs from Android
On desktop, v2rayN usually manages subscriptions under “Subscription group” → “Subscription group settings.” Edit the relevant group and look for an “Auto-update interval” field. The field name, unit, and whether updates need to be enabled separately depend on your version; check the current interface. Before saving, verify the subscription URL and update method. If the menu offers options such as “Update current subscription (without proxy)” and “Update current subscription (through proxy),” test the route with a manual update first.
The numbers below illustrate unit conversion and troubleshooting; they aren't a recommended interval for every subscription. Set the interval based on endpoint requirements, how often the configuration changes, and your device usage.
- Use the field's unit: If another guide says to enter 6, don't enter 6 in a field measured in minutes.
- Check what special values mean: Follow the field's instructions to find out whether a blank value, 0, or another special value disables updates. Don't guess based on experience.
- Keep the app running: The v2rayN timer isn't a continuously running system service when v2rayN is closed or your computer is asleep.
- Save settings on each device: The same subscription URL can be used on multiple devices, but update intervals and background permissions usually don't sync with the node list.
Bottom line: an interval can't fix a broken update path
First make sure a manual update succeeds reliably, then configure a schedule. If manual updates still time out or return errors, a shorter interval will only send more repeated requests; it won't fix an incorrect URL, permissions, or format.
Update succeeds, but the list is empty or nodes still don't work
After updating, check the selected group and any active filters before assuming nodes were removed. The interface may show only the current group, or a keyword filter may still be active. If no nodes were imported, check whether the subscription returned an empty response, the account expired, or the provider changed the output format. Don't paste the full response into a public forum; it may contain connection credentials.
The update succeeded, but nodes won't connect. Should I refresh again?
Stop repeating the update. Select a node, restart the connection, and check the connection log to distinguish DNS resolution errors, connection timeouts, TLS parameter issues, and server rejections. Subscription updates replace configuration; they don't confirm that the remote service is available or guarantee that the current routing rules send the target app through the proxy.
The same subscription updates in v2rayN but fails in v2rayNG. Why?
First use the same network and update method on both devices to rule out differences between direct and proxy routes, then verify that the URLs match exactly. If the download succeeds but parsing fails, ask the provider about the response format and protocol fields. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core; their parsing support differs, so the same subscription URL doesn't guarantee that every configuration is compatible.
Will an update immediately switch my active connection?
Not necessarily. The updated list, selected node, and running core configuration are separate states, and behavior varies by client version. To apply a new configuration, confirm which node is selected and reconnect using the interface. Avoid refreshing and immediately switching nodes during important transfers.
Use this checklist in order: confirm the subscription URL is complete, the account is active, manual updates work, the proxy update route is clear, the interval unit is correct, and background execution has been observed. Changing one thing at a time and recording the result makes issues easier to pinpoint than reinstalling the client, changing DNS, and deleting the group all at once. For import instructions, see the v2rayNG import guide. For response formats, see subscription formats and conversion.