Updating a subscription downloads a fresh node list; it does not test whether the nodes work. If v2rayN shows no new nodes after an update, update only the affected group first and check the logs to see whether the URL could not be reached, the server rejected the request, or the list was not imported. Set up automatic updates after a manual update succeeds.
First, Find Where the Update Fails
After receiving a subscription URL, the client must connect to the subscription server and then convert the response into nodes. Seeing old nodes in the window does not mean the latest update succeeded. Conversely, a successful update does not mean every node in the new list can connect. Check these separately.
Check the Group URL
In the v2rayN main window, open “Subscription Group” → “Subscription Group Settings” and edit the affected group. Make sure the URL is the subscription endpoint provided by your service, not a webpage from your account dashboard, and that no query parameters after the question mark are missing. If your provider recently reset the URL, save the new one first.
Update the Group Once
Select the group in the main window, then choose “Subscription Group” → “Update Current Subscription (without proxy).” Don’t update every group yet; this makes it easier to match any log error to the subscription you selected.
Check the Latest Log Entries
Find the last few lines for this update in the main window’s log. If you see a timeout or certificate error, troubleshoot the connection first. For an HTTP status code, check the server’s response. If the update completed but no new nodes appeared, check the response format and group filters.
Connection Timeouts and Certificate Errors
A timeout means the client did not complete a step within the allotted time; it does not mean the subscription has expired. A certificate error means HTTPS identity verification failed, and simply increasing the wait time will not fix it. Logs may show a generic message followed by a more specific cause, so focus on the final, specific error.
Connection timed out
Cause: The connection was not established before the timeout. The current network may not be able to reach the subscription domain, or the server may not be responding. What to do: First, check that a regular website opens on the same network. Then try updating the same group once on another trusted network. If it fails only on the original network, investigate that network’s route to the service; there’s no need to reset the URL first.
RemoteCertificateNameMismatch
Cause: The certificate received does not cover the domain being accessed. What to do: Check the full URL provided by your service, especially the domain and subdomain. Don’t replace the domain with the server’s IP address. If the URL is correct and the error persists on another network, ask your provider to check the certificate configuration for the subscription endpoint.
RemoteCertificateChainErrors
Cause: The system could not verify the certificate chain. Possible causes include an incorrect system clock, an expired certificate, an incomplete certificate chain on the server, or HTTPS inspection on the network. What to do: Check your system date, time, and time zone, then try again on a trusted network. If verification still fails, send the error to your provider or network administrator. Don’t disable certificate verification.
Invalid Subscription URLs and HTTP Status Codes
If the log shows an HTTP status code, the request received an HTTP response. Waiting a few more seconds usually won’t help. The same status code can mean different things on different services; use the codes below to decide what to check first, not as a definitive notice that your account has expired.
- 401: Copy the current subscription URL again from your provider’s dashboard. Check whether a URL reset invalidated the old credentials or whether a parameter was left out when copying.
- 403: Check your account status, whether the subscription is enabled, and whether your provider restricts clients or source networks. The server may reject a request even when the URL is correct.
- 404: Check that you’re using the correct subscription endpoint, especially if the domain changed and you’re still using an old path. Copying the full, current URL is more reliable than guessing the path.
- 429: The server is rate-limiting requests. Stop clicking Update repeatedly. If the response includes
Retry-After, wait for the specified time before trying again. Also check whether multiple devices are repeatedly refreshing the same URL.
Bottom Line: Check the Endpoint Before Switching Networks
For a clear 401, 403, or 404, confirm the subscription URL and your access with your provider first. Compare network routes only if the request gets no response, or if the same URL works on another trusted network.
Why Is the List Empty Even Though There’s a Response?
HTTP 200 only means the server returned a response; it doesn’t guarantee that the response is an importable list. A URL that redirects to a login page may still end with a 200 response. A page opening in your browser may simply mean you’re already logged in there—it doesn’t prove the client can retrieve the same content.
- Check the URL type: In your provider’s export options, choose a subscription explicitly intended for v2rayN. A webpage, login prompt, or full configuration for another client cannot be imported as a generic node list. If the response looks like an unreadable string, don’t assume it’s corrupted: some subscriptions encode the list.
- Check the group view: After the update completes, return to the group you updated and clear any search terms from the node list. If the group has filters, check that they haven’t excluded all the new nodes. Use the “All” view to help find nodes, but don’t mistake old nodes from other groups for newly imported ones.
- Tell an empty list from a parsing failure: Your provider may not have assigned any nodes to your account yet, or the output may contain entries the client can’t recognize. Confirm that nodes are present in your provider’s dashboard, then ask them to check the export format. Don’t delete an existing group that still works.
When to Update a Subscription Through a Proxy
“Through a proxy” only changes the network route used to fetch the subscription. It won’t fix an expired URL, an invalid certificate, or an unsupported response format. Use it to compare routes when the same URL and group can’t get a response over a direct connection, but you have a verified working proxy connection.
- In the v2rayN node list, select an existing node that can access the internet, and make sure the core is running. A node name in the list doesn’t prove it works; try accessing something to verify it rather than relying on a speed-test result alone.
- Switch back to the subscription group you want to update, then choose “Subscription Group” → “Update Current Subscription (through proxy).” Use this for a one-time test; there’s no need to change your system proxy mode or routing rules just to test a subscription.
- Check the log and group list for this update. If a direct connection times out but the proxy successfully imports the list, keep using the working option. If both methods return the same certificate or permission error, investigate the certificate or access permissions instead of blaming the update method.
Auto-Update Intervals and How to Verify Them
Auto-update fetches the subscription again at a set interval. It doesn’t reconnect nodes or retry every few seconds after a failure. Get a manual update working first, then set the interval; otherwise, one failure just becomes a recurring one.
- Set an interval for each group: Open “Subscription Group” → “Subscription Group Settings,” edit the group, and enter the number of minutes in “Auto-update interval (minutes),” then save.
1440means every 24 hours,360means every 6 hours, and0disables scheduled updates for that group. - Don’t treat the interval as a set time of day: 1440 minutes does not mean the update runs at midnight every day. It’s an interval while the client is running; don’t expect a subscription to refresh on time if the program has exited, the device is asleep, or the network is disconnected.
- Make sure scheduled updates work too: “Update Current Subscription (through proxy)” in the menu is a one-time manual action; it doesn’t save the network route for scheduled updates. If the subscription only works through a proxy, leave the client running after setting the interval and check the group’s update log at the next scheduled run. If scheduled updates still fail, update manually using the working method rather than hoping a shorter interval will help.