First determine whether the download failed, the response could not be parsed, or the nodes failed to connect. Then check link access, the update route, and your device’s clock. Set up automatic refresh only after a manual update succeeds. In the desktop client, check the group’s interval in minutes; on Android, confirm whether your version offers auto-update and what units it uses. Finally, verify that an update actually runs.
Where does the subscription update fail?
A subscription is separate from the proxy connection itself. The client requests the subscription URL, retrieves node details, and converts them into a local configuration. v2rayN handles subscription downloads in the client, so a running Xray core alone does not prove that subscription requests are going through the proxy. The system proxy, the subscription update command, and the client’s internal download settings are separate controls.
The point where the update log stops determines what to check. For a connection timeout, start with the network route. For HTTP 403, check authorization and server policies. If the download succeeds but no nodes appear, check the response format. Calling all three cases “dead nodes” can lead you to delete local configurations that still work.
| What you see | Check first | Don’t change yet |
|---|---|---|
| Request timed out or connection refused | Direct and proxy routes, active node, and local listening port | Node UUID and transport |
| HTTP 401, 403, or 410 | Account status, link token, and whether the subscription URL was reset | Routing rules and DNS split routing |
| Data received, but zero entries imported | Whether the response is a login page and whether the format is supported by the client | Auto-update interval |
| Import succeeded, but connections fail | Node connection logs, server status, and transport settings | The subscription download route that already worked |
Check the link and account status first
Subscription URLs often contain access tokens, so treat them like passwords. Copy the complete URL again from your provider’s account page. Don’t mistake a webpage URL, QR code image URL, or text truncated by a messaging app for the subscription URL. Resetting the subscription token may invalidate the old URL immediately. Nodes already stored in the client do not prove that the old subscription link still works.
-
Keep your existing configuration
First, note which nodes currently work and the names of their groups. While troubleshooting, don’t repeatedly delete entire groups or clear the full server list. If needed, use the client’s export feature to make a backup, and store files containing credentials securely.
-
Copy the URL again
Copy the subscription URL from your provider’s account page and replace the old one in the group. Check for leading or trailing spaces, line breaks, and complete query parameters. Don’t manually edit or remove tokens or parameters.
-
Update the group by itself
In the v2rayN main window, select the relevant group and choose “Subscription Groups” → “Update Current Subscription (without proxy).” Note the update time, status code, and error message. Menu wording and spacing may vary slightly by version.
-
Check your account status
Check whether the account has expired, its data allowance is depleted, or the subscription has been suspended. HTTP 403 can also indicate access policies or rate limits; the status code alone does not prove that the account has expired.
Know the difference between direct and proxy updates
If the subscription domain isn’t accessible directly on your current network, you can download the subscription through a node you’ve confirmed works. In v2rayN, start that node, then choose “Subscription Groups” → “Update Current Subscription (through proxy).” This makes it easier to tell which route the update uses than repeatedly toggling the system proxy. If you don’t have any working nodes left in the list, updating through a proxy can’t restore the connection on its own.
- Direct update works, proxy update fails: Check the active node, the client’s local proxy listener, and whether the subscription service restricts exit IPs. You can keep using the direct route; there’s no need to force all subscription updates through a proxy.
- Direct update fails, proxy update works: The two routes behave differently. Check which download method auto-update uses; don’t assume that choosing a method once for a manual update permanently changes background tasks.
- Both methods return the same HTTP error: Check the URL and server response first. Changing DNS or ports is unlikely to fix an authorization issue.
- Both methods time out: Check that the network has internet access, the node works, and the device isn’t on a network that requires you to sign in through a web page.
Use the port shown in your actual settings. For example, if the HTTP proxy listens on 127.0.0.1:10809, sending a request to 127.0.0.1:10808 may reach a different type of proxy port or be refused. These numbers are examples for troubleshooting, not universal defaults. Check the local listener settings in v2rayN under “Settings” → “Parameter Settings,” then compare them with the runtime logs.
Narrow it down using the exact error
Open the client’s information or log panel and copy the full error line from around the time of the subscription update. Don’t rely only on the “Update failed” notification. The examples below are possible underlying errors; exact wording varies by environment and client version. Diagnose by error type rather than expecting an exact match.
Response status code does not indicate success: 403 (Forbidden).
Cause and fix: The server rejected the request. This may involve the token, account status, or access policy. Copy the subscription URL again from your account page, stop retrying repeatedly, and ask your provider why the request was rejected.
The operation has timed out.
Cause and fix: The request did not complete in time. Compare direct and proxy updates first, then check the active node and network. Increasing the timeout alone won’t make an unreachable URL accessible.
No such host is known.
Cause and fix: The domain could not be resolved. Check the subscription domain spelling, device DNS, and network connectivity. If the update request never enters the core, changing the core’s dns.servers may not affect this DNS lookup.
The remote certificate is invalid because of errors in the certificate chain: NotTimeValid
Cause and fix: The certificate validity check failed. The device clock may be wrong, or the server certificate may have expired. Sync the device’s date and time, then try again. If the error persists with the correct time, the subscription service operator should check the certificate.
Connection refused
Cause and fix: The destination did not accept the connection. If the log points to the local machine, check whether the core is running and the port matches. If it points to a remote subscription server, check the remote service status. Don’t change node authentication fields without reason.
On Windows, go to “Settings” → “Time & language” → “Date & time,” turn on automatic time setting, and sync the clock. On Android, the path is usually “Settings” → “System” → “Date & time,” though some devices place it under a different system settings category. Certificate errors can also result from HTTPS inspection on the network or an invalid certificate chain. Don’t bypass them by disabling certificate validation.
- Note the local time of the error and which update method you used so you can compare it with server logs.
- If the response is an HTML login page, CAPTCHA page, or maintenance page, it is not a valid node subscription—even if the HTTP status is 200.
- If the download succeeds but VMess or VLESS entries can’t be parsed, check whether your provider offers a subscription format supported by your client, then check the client version.
Set the v2rayN auto-update interval
Run a successful manual update before enabling scheduled refresh. In common desktop versions of v2rayN, subscriptions are managed under “Subscription Groups” → “Subscription Group Settings.” Edit the relevant group and look for “Auto-update interval (minutes).” The steps here refer to an interface that displays this field. If your version uses a different field or unit, follow the actual label—don’t enter hours into a field that expects minutes.
-
Open the target group
Go to “Subscription Groups” → “Subscription Group Settings” and edit the group you want to refresh regularly. Check the note and subscription URL first so you don’t change a different group with the same name.
-
Enter the interval in minutes
For “Auto-update interval (minutes),” start with
360, or 6 hours. This is a suggested starting point, not a universal default. Follow any lower request-frequency limit set by your provider. -
Confirm the download route
If your version has an option such as “Update through proxy,” set it to match the method that worked earlier. If there’s no separate option, check the subscription download settings for that version and use the logs to verify that the background task succeeds.
-
Save and monitor
Save the group, leave the program running, and check the subscription log when the next update is due. Don’t judge success only by the node count: a successful update may leave the count unchanged if the content hasn’t changed.
| Desired interval | Value for the minutes field | When to use it |
|---|---|---|
| 6 hours | 360 | For cases where you need node changes to show up promptly |
| 12 hours | 720 | Reduce requests when nodes rarely change |
| 24 hours | 1440 | Check for changes daily, taking program uptime into account |
Auto-update depends on the program running and the system scheduler; it is not a push from the server. Don’t expect tasks to run right on schedule while v2rayN is closed, or the device is shut down or asleep. Don’t assume 0 means “update now”: in many interfaces, it disables scheduled updates. Read the field description before saving.
v2rayNG refresh and background limits
On Android, v2rayNG uses the Xray core, but subscription management is still handled in the client interface. Open “Subscription Group Settings” from the main screen menu, make sure the target group is enabled and its URL is correct, then return to the menu and choose “Update Current Group Subscription.” If your interface uses a label such as “Update Subscription,” confirm whether it updates the current group or all groups.
-
Start with a manual refresh
Connect to a working node, update the target group, and check the update notice and node list. Whether Android downloads through the current proxy depends on the version and settings, so verify it from the result.
-
Check for the setting
Check “Settings” and the target group’s edit screen for an auto-update toggle and interval. Features and menu locations vary between v2rayNG versions, so don’t copy the minutes field from v2rayN.
-
Check the interval unit
If your version offers an interval setting, follow the field label and choose 6 hours or an equivalent value. Enter
360only if the field specifies minutes. After saving, wait for an actual update to confirm that the setting does more than enable a toggle. -
Check background permissions
Go to “Settings” → “Apps” → “v2rayNG” → “Battery” and check for background activity restrictions. The exact labels depend on your device. Allowing background activity still doesn’t guarantee that updates will run to the minute while the screen is locked.
Verify the update and troubleshoot common questions
A successful subscription update means the node descriptions were saved locally; it doesn’t mean every node can connect. After updating, check the group, selected node, and logs, then test an actual connection. If your provider removed or renamed a node, confirm your current selection so you’re not still trying to use a removed entry.
The update succeeded. Why is the node count unchanged?
The server’s content may not have changed. Check the success message, then see whether node addresses or notes in the group were updated. Don’t require the count to increase as proof of success, and don’t keep clicking refresh to check.
I set 360 minutes. Will it update while the computer is off?
No. A stopped client can’t run the update. After turning on the computer, start v2rayN and update manually if needed. Whether it catches up on missed tasks or starts a new interval depends on the current version.
Manual updates through a proxy work, but auto-updates fail. Why?
Check whether a node is running when the scheduled task starts and whether background updates use the same route. Review the log for the scheduled time. If the client hadn’t established a connection then, restore a working node before refreshing manually.
Should I change the interval to one minute after getting a 429?
No—don’t shorten it. HTTP 429 means the request was rate-limited. Stop retrying, wait as instructed by the server, and if the response includes Retry-After, make the next request after that time. Consider lengthening the auto-update interval.
Does auto-update switch nodes automatically?
Refreshing a subscription and selecting a node are separate actions. Refreshing updates node data; it doesn’t automatically select the node with the lowest latency. If the selected entry was removed, go back to the target group, choose an available node, and check the connection log.
Keep a concise troubleshooting record: the time of the issue, target group, direct or proxy route, HTTP status, and entry counts before and after the update. This is usually more useful than repeatedly reinstalling the client. For more on how the system proxy differs from core routing, read the Getting Started guide and configuration reference.