This article explains how to add a subscription in v2rayNG, what to do if no nodes appear afterward, and how teams can reduce frequent changes to their connection environment. A subscription URL is a link for retrieving a node list, not a website login address. Adding a subscription does not connect you automatically: you still need to update the nodes, select one, and start the proxy.
1. Before you begin: check the client and subscription link
v2rayNG is designed for Android. We recommend installing it from a trusted source, such as the project’s official GitHub releases page, and avoiding modified versions from unknown sources. If you already have the client installed, note its version and save your existing configuration before troubleshooting. Don’t rush to clear the app’s data.
Get the complete subscription link from your service provider. When copying it, make sure you don’t include spaces, line breaks, or Chinese punctuation. A subscription URL may contain access credentials, so treat it like a password. Don’t post it in public groups or include it in screenshots or support tickets. The free nodes available on this site can be used for learning and connectivity tests, but availability may change. Don’t rely on them as your team’s sole connection for critical business operations.
2. How to add a subscription in v2rayNG
- Open v2rayNG, tap the menu in the upper-left corner, and find “Subscription group settings” or a similarly named subscription management option. The interface may vary slightly between versions.
- Tap “+” in the upper-right corner. Enter an easy-to-recognize name in the remarks field, such as “Daily work,” paste the complete link into the subscription URL field, and save.
- Return to the node list, open the menu in the upper-right corner, and select “Update subscription” or “Update subscription for current group.” Wait for the result. Saving the URL alone usually won’t automatically add any nodes.
- After the update succeeds, tap a node to select it, then tap the connect button. The first time you connect, Android will display a VPN connection request. Confirm it to establish the system VPN tunnel.
- Test the connection by opening the site you want to use. If only some apps are accessible, check the routing mode and per-app proxy settings, and make sure the app hasn’t been excluded. This can help you avoid mistaking a routing issue for a node failure.
Update the subscription first, then select a node and connect. This sequence is easy for new users to overlook. The VPN icon means the tunnel has started; it doesn’t necessarily mean the remote node is working.
3. Troubleshooting failed subscription updates and connection issues
- Update fails: Check that the link is complete and hasn’t expired, and that your current network can reach the subscription service. If necessary, ask the provider for a new link. Don’t submit your link to an unfamiliar online conversion site.
- Update succeeds, but no nodes appear: Make sure you’ve selected the correct group, and ask the provider whether the subscription format is supported by your current version. A webpage URL or login page can’t be used as a subscription URL.
- Nodes appear, but won’t connect: Make sure your phone’s time is set to update automatically, try another node, and compare the results over Wi-Fi and mobile data. If another VPN is enabled, turn it off temporarily to rule out a conflict.
- Some websites behave unexpectedly after connecting: Check your routing and DNS options. For a reliable test, restore the client’s default settings first, then change one setting at a time to help identify the cause.
4. How does team use relate to account environment stability?
A subscription is simply a way to update your node list. Adding a subscription won’t, by itself, make a business account more stable. Frequently switching between exit locations may trigger login verification for some platforms. Sharing a subscription also doesn’t mean every team member will have a fixed, identical exit IP.
Teams should assign access in accordance with the provider’s terms and platform rules. Each member should stick to their usual device and an appropriate connection, and avoid switching locations repeatedly just for testing. If a login requires verification, follow the platform’s process rather than trying to bypass it by changing nodes. If a subscription is exposed, contact the provider promptly to reset it, then update the client configuration.