If an update times out, compare direct and proxied updates for the same group. If the request succeeds but imports no nodes, check the response and group filters. This guide is for users who have already added a subscription in v2rayN. Run one manual update to narrow down the issue, then configure the auto-update interval.
Subscription update failed: distinguish request errors from empty results
When v2rayN updates a subscription, it first requests the subscription URL, then parses the response into nodes. Existing nodes may still work even when the subscription URL has expired, and a successful update request does not guarantee that the response contains importable nodes. Select the affected group and run one manual update. Find its entry in the main window's messages or in the logs; don't mistake a node latency-test error from the same time for a subscription error.
Bottom line: Check the status code before deciding what to troubleshoot
If you received an HTTP response, use the status code to investigate server permissions or the response body. If you only see a timeout or connection error, compare the two update methods first. For a 429 response, stop retrying and wait for the time specified by the server before trying again.
Update timed out? Compare direct and proxied requests
These steps use the simplified Chinese interface in the v2rayN 7.x desktop client. Menu wording may vary slightly between versions; look for the current subscription and choose between “through proxy” and “without proxy.” The system proxy setting is for applications to use. Choose the route for this update from the update menu itself—don't rely on the system proxy icon alone.
Check the group
Select the affected group in the main window, then go to “Subscription groups” → “Subscription group settings” and check its URL. Compare it with the full link on your provider's account page. Check for accidental line breaks or missing parameters after the question mark. Keep the existing group and any working nodes; don't delete the group just to test.
Test without a proxy
Select “Subscription groups” → “Update current subscription (without proxy)” and note the time and result. If you get a 403 or 429, check your access or wait for the rate limit to clear. If it times out after waiting without returning an HTTP status code, compare with a proxied update.
Verify the proxy
Set an existing working node as the active server, then use an application explicitly configured to use the local proxy to open a regular webpage. Enter the host, port, and proxy type shown in your current client settings. For example, if the settings show a SOCKS listener at
127.0.0.1:10808, connect using SOCKS—don't treat the same address as an HTTP proxy.Test the subscription again
Keep the same subscription URL and network, then select “Subscription groups” → “Update current subscription (through proxy).” If only the proxied update succeeds, the link is reachable through your current proxy. If only the direct update works, keep using direct updates; there's no need to change the system proxy setting for every application.
Check the result
When the update finishes, return to the group, clear the search field in the main window, and check the node list. If both methods fail, save the last error from each along with its timestamp. You can't compare proxy routes if there are no working nodes; troubleshoot without a proxy first, or ask your provider whether the link is accessible on your current network.
Update logs: find the cause in the exact error message
Error wording varies by operating system, interface language, and runtime. You may see the English snippets below in the exception details. If an exception contains multiple layers, start with the most specific inner error and confirm that it belongs to the update you're troubleshooting.
Error: No such host is known.
Cause and fix: A hostname somewhere along the request path couldn't be resolved. It could be the subscription domain or a hostname used by the proxy route. Check the log to identify which host failed, then verify that address. If direct DNS resolution fails but the update works through a proxy, there's no need to change the device's DNS settings just for this subscription.
Error: Response status code does not indicate success: 403 (Forbidden).
Cause and fix: The server rejected the request. Your subscription credentials may have expired, or the server may restrict access by source. Check your provider's account page to confirm the subscription is active and copy the link again. If the 403 occurs on only one update route, give your provider the route and error timestamp so they can investigate.
Error: The operation was canceled.
Cause and fix: The request was canceled, possibly because it timed out, the client was closed mid-update, or the network changed. Keep the client running on a stable connection and update the affected group once on its own. Troubleshoot a connection timeout only if the log specifically reports one or repeated attempts fail after waiting.
Update completed but no nodes appeared? Check the response format and filters
An HTTP 200 response only means the server returned a successful response. An expired subscription URL may still return a login page or notice with status 200. A successful visit in your browser also doesn't prove the client received the same content: the browser may have an active login session, or the server may return different formats based on request headers.
| What you see | What to do next |
|---|---|
| A login page or account notice appears | Copy the subscription URL intended for use in a client from your account page. Don't enter the account management page URL in the group settings. |
| The response body is empty or only shows a provider notice | Check your plan status, whether nodes are still assigned to the subscription, and whether a reset invalidated the old link. |
| The response has content, but the client imports no nodes | Ask your provider which format the link uses, then copy the option explicitly marked for v2rayN. A list of share links may be plain text or encoded as a whole in Base64; don't assume a format is valid just because the text looks encoded. |
| The log says nodes were imported, but the list is empty | Return to the group you just updated and clear the list search field. If the group settings include a regular expression for filtering nodes, note its current value, clear it temporarily, and test again. |
Subscription URLs may contain access credentials in their paths or query parameters. Don't submit the full URL or response body to an online decoding tool. When contacting your provider, include the update method, error time, and status code, and redact any account-identifying details in the link.
Auto-update interval: configure each group and verify in the logs
First confirm that a manual update succeeds. Then go to “Subscription groups” → “Subscription group settings” and edit “Auto-update interval” for the target group. The value is in minutes: 1440 means 24 hours, 720 means 12 hours, and 0 disables auto-updates for that group. Follow your provider's recommended interval. If they haven't specified one, start with once a day; shortening the interval won't fix connection problems.
- Reopen the group settings after saving. Confirm you edited the affected group, that the group is enabled, and that the interval value and units are correct. Check the interval for each subscription group separately.
- Check the client is running when the update is due. Keep v2rayN open and compare log timestamps around the due time. Auto-updates run periodically while the client is open; they aren't scheduled for a fixed time of day and won't run after the program exits.
- Test auto-updates separately from manual updates. “Through proxy” and “without proxy” in the manual update menu apply to that operation only; they aren't persistent settings for scheduled updates. If your version has a separate proxy option for auto-updates, configure and test it. If not, use the logs around the due time and the active node at that time to verify behavior. A successful manual update doesn't verify auto-updates.
FAQ: Working nodes and update rate limits
My old nodes still work, but updates fail. Should I delete and re-add them?
Don't delete them yet. Working nodes mean the current configuration is usable, not that the URL for downloading an updated list is valid. Check the link and update the existing group first. To test a new link, add a temporary group and confirm it imports before deciding whether to replace the old one.
Auto-update returned 429. Can I just click update again?
Stop and wait. Temporarily set that group's auto-update interval to 0. If the server returns Retry-After, wait until the specified time, then try one manual update. When you re-enable auto-updates, use a longer interval as recommended by your provider to avoid multiple devices refreshing the same subscription at once.
Node latency tests are delayed. Why does the subscription still time out?
A latency test and a subscription download connect to different destinations. First confirm that the active node lets an application explicitly configured to use the local proxy open a webpage, then compare using “Update current subscription (through proxy).” If regular webpages load but the subscription still times out, note the subscription domain, time, and update method, then ask your provider to investigate the request.