If a subscription update fails, a group does not refresh, or fewer nodes appear after an update, manually update one group first. This helps distinguish download failures from parsing errors and connection problems after an update. v2rayN and v2rayNG users can use these checks to verify the subscription URL and request route, then decide whether to enable scheduled refreshes for that group.
First, identify whether the failure is in downloading, parsing, or connecting
A subscription URL is what the client uses to retrieve a list of nodes; it is not the server address of any node on that list. A successful refresh only means the client retrieved and processed the subscription data—it does not mean every node can connect. Likewise, an inaccessible subscription URL does not immediately invalidate nodes already saved in the client. Keep the existing list while troubleshooting, and do not delete the group just to test the link.
- URL request failed: Copy the full subscription URL again from your provider's dashboard. Check for leading or trailing spaces, line breaks, and query parameters. Do not use an account login page, an individual node share link, or a converter's preview page in place of the subscription URL.
- Request succeeded, but no nodes were imported: HTTP 200 only means the server returned a response. A login page, maintenance page, or verification page can also return 200. Confirm that your provider supplied a subscription format the client can import, then check whether group filters excluded the entries.
- Nodes updated, but won't connect: Select a newly added node from the group and test it on its own, then check the connection log. Verify the node address, transport settings, and core compatibility. Shortening the subscription refresh interval will not fix a failed handshake.
Subscription error logs: timeouts, parsing, and certificate errors
Refresh only the group that failed, note when you clicked the update button, and check the client message from that same time. Error wording varies across operating systems and versions; the examples below are common messages or exception names. First distinguish subscription request errors from node connection errors in the core's runtime log.
java.net.UnknownHostException
Cause: The client could not resolve the hostname. The URL may be incorrect, or DNS resolution may be failing on the current network. Fix: Check the subscription hostname, then try the same group on another trusted network. Avoid changing node settings and DNS at the same time.
java.net.SocketTimeoutException: timeout
Cause: Connecting or reading the response took longer than the allowed wait time. This message alone does not mean the subscription has expired. Fix: Keep the same subscription URL and compare one attempt over your current direct connection with another through a confirmed working proxy. Note which route completes the download.
The SSL connection could not be established, see inner exception.
Cause: This is a general TLS connection failure. Check the underlying exception to tell whether the issue involves the certificate date, hostname, or chain of trust. Fix: Sync your system date, time, and time zone, then try again. If the error persists, send the provider the underlying exception with sensitive details removed. Do not disable certificate verification.
If both routes return 401 for the same group, replace the link first
Get the subscription URL again from your provider's dashboard, replace it in the existing group, and refresh manually once. If you get a 429 response, wait as directed by the Retry-After response header or your provider. Repeatedly clicking Update makes the next test harder to interpret.
v2rayN: Update a subscription and set the refresh interval
In v2rayN, open subscription group management or start an update from the 「Subscription Group」 menu on the main screen. The steps below refer to the commonly used Chinese interface; wording may vary by version, so check the actual menu labels and the units shown next to each field. For an initial check, update only the current group so you can match the result to its log.
Check the group URL
Go to 「Subscription Group」→「Subscription Group Settings」, open the target group, and verify its remarks and subscription URL. If your provider has reset the link, replace the URL in the existing group and save it. This avoids keeping the old and new links as separate groups to update.
Test an update without a proxy
Return to the main screen, select the target group, and choose 「Subscription Group」→「Update Current Subscription (Without Proxy)」. Check the message and the target group's node list. If entries are missing, review the group's filter settings and then check the data supplied by your provider.
Compare with an update through a proxy
If the direct update times out, first confirm that an existing node connects and your local proxy is running. Then compare using 「Subscription Group」→「Update Current Subscription (Through Proxy)」. If both methods fail, note each error. Updating through a proxy is not a universal fix for authentication or certificate errors.
Set the refresh interval
After a successful manual update, return to the group's edit screen and check the 「Auto Update Interval」 field. The value is in minutes: enter
1440for 24 hours. If your provider requires a longer interval, follow its instructions. Save the setting, leave the client running, and check the update log after the next scheduled cycle.
A successful manual update using 「Through Proxy」 does not mean scheduled tasks will use the same route. If manual updates work but scheduled ones fail, check the log for the scheduled time. Confirm the client was running, the machine was not asleep, and the network or local proxy needed by the scheduled request was available. An unchanged group may be expected; node count alone does not confirm whether a refresh occurred.
v2rayNG: Refresh groups and check auto-updates
In v2rayNG, open the side menu on the main screen and go to 「Subscription Group Settings」. Edit the target subscription, check its URL, and confirm that the group is included in updates. Save, return to the node list, switch to the target group, then tap 「Update Subscription」 in the top-right 「⋮」 menu. Menu options vary by version: use an option for updating the current group if available. If only a full update is offered, check the results and group list; do not mistake results from other groups for the target group's results.
- Set up scheduled refreshes: In the 「Subscription Group Settings」 edit screen, check whether your version has an auto-update toggle or interval. If the setting is global, enable it and confirm that the target group is included. If there is an interval field, enter one day's value in the units shown, such as
24hours or1440minutes. If the app has no scheduled update option, refresh manually; do not apply desktop menu steps to the mobile app. - Check the request route: Subscription refreshes are network requests made by the client. Even if the system says the connection is active, its icon alone cannot tell you which route the subscription hostname uses. App-specific routing, the current network, and the client implementation can all affect the result. Change one condition at a time during comparisons, and keep the same subscription URL.
- Check background execution: If a manual update works in the foreground but no scheduled update is logged, check whether Android restricts background activity or delays tasks in battery-saving or standby modes. First confirm that your version supports scheduled updates, then check system restrictions. Changing battery settings alone cannot add a scheduling feature to the client.
Auto-refresh frequency and how to verify results
If your provider does not recommend an interval, start with one full 24-hour cycle as a test. There is no need to keep shortening the interval for a stable group just to get updates sooner. If multiple devices share a subscription, stagger their refresh times to avoid a burst of requests using the same credentials. Follow your provider's recommended refresh frequency over any general guidance.
- Record a baseline: Refresh manually once and note the group name, successful update time, and number of node entries. Do not include the full subscription URL in screenshots or public logs; query parameters may contain access credentials.
- Verify the next scheduled run: When the scheduled interval has passed, check the client notification or update log. If the content has not changed but the log confirms the request and parsing succeeded, there is no need to shorten the interval. If the update only appears after launching the client, check whether the task runs only at startup or when the app resumes.
- Adjust based on the issue: If you are rate-limited, lengthen the interval or temporarily disable scheduled updates. If your provider asks you to reset your credentials, replace the URL in the existing group. If only one group fails, fix that group rather than rebuilding your other subscriptions.