For users who have imported a subscription but see a timeout or an empty list after updating. First, manually update one group in v2rayN to tell a request failure from a parsing failure. Once manual updates work, set an auto-update interval for that group.
Update one group first and note the first error
A subscription update fetches a list of configurations; it does not test the nodes in that list. An old node may still connect even if the subscription URL has expired, and a successful refresh does not mean every new node will connect. Note which nodes currently work and record the existing group settings. Don’t delete the old group yet.
- These steps use the v2rayN 7.x desktop interface. On the main screen, select the affected subscription group, then use the option for updating the current subscription in the “Subscription Group” menu. Don’t choose Update All; logs from multiple groups can be hard to distinguish.
- Note whether you updated directly (without a proxy) or through a proxy, then find the first error associated with that operation in the message panel. If the only message is that the update failed, expand its details. Don’t mistake node speed-test results that appear afterward for subscription errors.
- If the interface reports success, make sure the target group is selected and clear any search filters before checking the node list. It’s normal for the number of nodes to stay the same; an unchanged count does not prove the update failed.
Expired URLs, access errors, and unsupported formats
Open the affected group under “Subscription Group” → “Subscription Group Settings” and compare its URL with the complete, current URL shown in your provider’s account portal. Copying it again is safer than editing it manually: parameters after the question mark may be required for authorization, so don’t keep only the domain and path. Chat apps may also copy a line break or trailing punctuation. Don’t use the provider’s login page or a shared node link as the subscription URL.
| What you see | Check first | What to do next |
|---|---|---|
| HTTP 401 or 403 | Authorization, account permissions, or server access policy | Sign in to your provider’s account portal and check the subscription status. If a new URL still returns an error, give the provider the status code and time it occurred. |
| HTTP 404 or 410 | The path changed, the URL was revoked, or the resource was removed | Get the URL again from your account portal. Don’t keep retrying the old link. |
| HTTP 200, but no usable nodes | The response may be a login page, notice page, empty list, or configuration format the client doesn’t support | Use the subscription option your provider identifies as compatible with your client, then try updating again. |
| HTTP 429 | Rate limit reached | Stop clicking Update repeatedly. If the response includes Retry-After, wait as directed, then increase the auto-update interval. |
Bottom line: after a response arrives, check whether its contents can be imported
If the request returns 200 but no nodes are parsed, first check which subscription type your provider issued. Don’t switch the core as a first step. An HTTP success only means a response was received; it doesn’t mean that response contains node configurations the client supports.
Timeouts, blocked requests, and incorrect system time
If the request receives no HTTP status code, check the error details to see whether the problem is DNS resolution, the connection, or certificate validation. The following English snippets may appear in low-level errors; the surrounding message can vary by operating system and client version.
No such host is known.
Cause: The domain couldn’t be resolved along the request path. A mistyped URL or a network DNS issue can cause this. Fix: Copy the link again from your provider’s account portal, then try the same update over another network you’re authorized to use.
Connection refused
Cause: The destination port refused the connection. When updating through a proxy, the refused connection may be to the local proxy port. Fix: Check whether the error points to a local or remote address. If it points to 127.0.0.1, make sure the core is running and check the local listening port shown in the client. Don’t copy someone else’s port number.
certificate has expired or is not yet valid
Cause: The certificate used for validation may have expired, may not yet be valid, or the device clock may be incorrect. Fix: Sync your system clock and try again. If the time is correct and the error persists, contact your provider or network administrator. Don’t disable certificate validation.
- In Windows 11, open “Settings” → “Time & language” → “Date & time.” Check the time zone and current date, turn on “Set time automatically,” then select “Sync now.” After that, manually update the current group; there’s no need to change the subscription URL first.
- If the request times out only on one network, check whether that network requires a web sign-in or allows the client to connect to the subscription service. Keep the URL and update method unchanged while testing on another network you’re authorized to use. Avoid changing multiple variables at once.
- If proxy use is allowed on your network and you already have a working node, use the option to update the current subscription through a proxy in the “Subscription Group” menu for comparison. Conversely, if a direct update works but an update through a proxy fails, check the local proxy listener and selected node rather than resetting the subscription.
Set the v2rayN Auto-Update Interval
Once a manual update succeeds for the group, configure its scheduled updates. In the v2rayN 7.x desktop app, edit the target group under “Subscription Group” → “Subscription Group Settings,” then find the auto-update interval field, which is measured in minutes. The field name may vary by version, so check the unit shown in the interface before entering a value: for minutes, 24 hours is 1440, not 24.
- Enable auto-updates: If the current interface has a separate “Enable updates” option, make sure it’s enabled for that group, then save a positive interval. If the interface says
0disables auto-updates, leave it at0only when you want to update manually. Check each group individually; changing only the selected group won’t update them all. - Choose an interval: If your provider hasn’t specified a frequency, start with
1440minutes. If you need updates within half a day and your provider allows it, try720minutes. These are example intervals, not client defaults. If you hit a rate limit, follow your provider’s guidance first. - Check the auto-update request route: Choosing “Through proxy” from the manual menu doesn’t mean scheduled updates will use the same route. If your version has an option for the auto-update request route, make sure it matches the method you’ve verified works. Otherwise, check the auto-update logs before switching back to manual updates.
- Confirm the scheduled task runs: After saving, keep the client running and avoid closing the process or letting your computer sleep for long periods while testing. Check the message log or the group’s last-updated time after the scheduled update is due. If it didn’t run, check the process and group settings instead of repeatedly shortening the interval.
Frequently Asked Questions About Subscription Updates
Why can I open the URL in a browser but not update it in the client?
The browser may still be signed in, or it may use a different proxy route. Copy the dedicated subscription URL from your provider’s account portal, then check the client log. If it reports an access error, verify your subscription credentials. If it reports success but shows no nodes, check the response format; a browser page title doesn’t confirm that the format is supported.
Do I need to delete the old group before changing the subscription URL?
No. If your provider specifically says to replace the URL, edit the relevant group in Subscription Group Settings and run a manual update. If you’re concerned the new URL may return the wrong content, test it in a temporary group first, then tidy up the old group once you’ve confirmed the configuration works. An update may replace the group’s contents, so don’t treat it as the only backup of manually configured settings.
Why does it update on Android but not on my computer?
First check that both devices use the same subscription option, then update them under the same network conditions. v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. A node that imports and runs on one device may use a configuration the other doesn’t support. Compare the subscription update results on both devices before troubleshooting the node connection separately.
Will a failed auto-update immediately disconnect my current connection?
A failed update request isn’t the same as a dropped connection. Check the main screen to see whether the old node is still listed and whether the selected node works. If a node disappeared after a successful refresh, check whether it’s still in the new list, then test another working configuration from that group. Don’t keep refreshing repeatedly.
Clients and Subscription Settings
Choose a download option for your operating system, or follow the guide to check your subscription group and update steps.