At a glance

For users who have added a subscription group but still don’t see new nodes after an update. First, manually update the same group to determine whether the request failed or the response couldn’t be parsed. Once manual updates work, configure automatic updates. Keep any working old nodes while troubleshooting; don’t delete the group first.

First, find out where the update fails

A subscription update downloads a node list from the server. A connectivity test uses one of the nodes in that list to establish a connection. These are separate operations and can have different results. A working old node doesn’t mean the subscription URL is still valid, and a successful list download doesn’t mean every node in it is online.

Load subscription groupResolve domainEstablish connectionDownload dataParse nodes
  1. Check the group

    In the v2rayN main window, open “Subscription Group” → “Subscription Group Settings” and select the affected group. Check that the subscription URL matches the current URL in your provider’s dashboard, including the domain, path, and any query parameters. Individual VMess or VLESS node links should be imported as nodes, not entered as subscription URLs.

  2. Update the group on its own

    Return to the main window, select the target group, then choose the command under “Subscription Group” whose name includes “Update current subscription.” If your version only offers an option to update all subscriptions, identify the relevant log entry by group name. Run the update once; repeated clicks can mix results from multiple attempts.

  3. Note the first error

    Check the main window’s log or status area and note the update time, group name, and first specific error. Before sharing a screenshot, hide the full URL, account identifiers, and query parameters. A token in a subscription URL usually grants access, so don’t paste the URL into an online parser.

Invalid URLs, network timeouts, and certificate errors

Start with the most specific error in the log. Messages vary between clients and runtime environments. If the interface only says “Update failed,” expand the details and look for an HTTP status code, timeout, or TLS certificate message.

Error: 401 Unauthorized

Cause and fix: The server rejected the request credentials. Sign in to your provider’s dashboard and check your account status. Copy the current subscription URL again, replace the old URL in the existing group, and update it manually. If the old link was exposed, revoke or reset its token in the dashboard first.

Error: 404 Not Found

Cause and fix: The server didn’t find a resource at that path. Check whether you copied an outdated endpoint or missed the end of the URL. Copy the full URL from your dashboard again; don’t try to guess the path.

Error: The operation has timed out.

Cause and fix: The request didn’t finish in time. This message alone doesn’t tell you whether DNS resolution, the connection, or the response was slow. First, change only the network path and compare the results. If the log also says the domain couldn’t be resolved, check whether your current network can resolve the subscription domain instead of changing the node protocol.

Error: RemoteCertificateNameMismatch

Cause and fix: The hostname doesn’t match the one covered by the certificate. Check the subscription URL and any domain it redirects to; don’t replace the domain with the server’s IP address. If the new URL from your dashboard still triggers the error, send the provider the redacted domain and error so they can check the certificate.

Error: RemoteCertificateChainErrors

Cause and fix: Certificate chain validation failed. First, sync your system date, time, and time zone. Then check for a network sign-in page or organization-managed HTTPS inspection. If the issue persists on multiple networks, ask your provider to check the certificate’s validity and intermediate chain. Don’t disable certificate validation.

Compare update results with and without a proxy

The “Subscription Group” menu in v2rayN may offer separate commands to update “Without proxy” or “Through proxy”; wording varies by version. Keep the subscription URL and group unchanged for both tests. Before choosing “Through proxy,” confirm that the selected old node works and the local proxy listener is running. Don’t infer the local proxy port from port 443 in the subscription URL: one is for accessing the remote subscription server, the other for receiving proxy requests on your device.

ResultNext step
Times out without a proxy, succeeds through a proxyThe direct connection may be the problem. Test the same URL on another trusted network; there’s no need to change the subscription format first.
Succeeds without a proxy, fails through a proxyCheck the selected node and local listener first. If the log says the connection was refused, make sure the listener port matches the client settings.
Both methods return 429Stop retrying repeatedly. If the response includes Retry-After, wait as instructed by the server and increase the auto-update interval.
Returns 200, but no nodes are importedCheck whether your provider offers a subscription format supported by this client. A sign-in page, error message, or even an empty list can also return 200.

Bottom line: If both methods return the same status code, check the server response first

If both attempts return 401, get a fresh URL from your dashboard and check your account status first. Changing the local port or shortening the auto-update interval won’t fix invalid credentials.

Auto-update intervals in v2rayN and v2rayNG

Auto-update periodically fetches the list; it won’t turn a failed request into a successful one. First, run a manual update and confirm that the log shows it completed and the list contains the expected content. Then set the interval using the field and units shown in your client. Don’t copy desktop values directly into the Android version.

Subscription update FAQs

Why does the client report a parse error when the URL opens in a browser?

The browser may already be signed in or may follow a redirect to a web page, while the client receives something other than a node list. Copy the subscription URL intended for clients from your provider’s dashboard, not the account page URL. After updating, check the log for a message confirming that nodes were parsed, not just downloaded.

The update completed, so why do I still see the same nodes?

First, make sure you’re viewing the group you just updated, not a group with manually added nodes. Then compare the list with the node changes announced by your provider. If the source list hasn’t changed, it’s normal for the node count and names to stay the same after a refresh. Test node connectivity separately.

It works on my computer, but Android keeps timing out. What should I check first?

Connect both devices to the same trusted network and manually update each one using the same subscription URL. If Android still fails, check the group URL and your phone’s date and time, then review the client’s specific error. Check background restrictions and update options first only if manual updates work but automatic ones don’t.