This guide explains how to add a v2rayNG subscription. It walks you through importing and updating a subscription, selecting a node, and testing the connection on an Android phone. It also explains how node switching relates to account environment stability when a team uses the service. A subscription is only a way to obtain node configurations; it does not guarantee a fixed exit IP or prevent an account from triggering security checks.
1. What to prepare before adding a subscription
Download the installer from the official v2rayNG project release page and follow your phone’s prompts to install it. Avoid modified versions from untrusted sources. Have the subscription link provided by your service provider ready. It is usually a URL that begins with https://. A single vmess://, vless://, or trojan:// link is generally a node-sharing link, which uses a different import option.
A subscription URL may contain a personal token, so treat it like a password. Don’t post it in public group chats or include it in screenshots. Before using a subscription with a team, also confirm that the service allows sharing and use on multiple devices, and avoid having multiple people share a single sensitive subscription URL.
2. Steps to add a v2rayNG subscription
- Open v2rayNG, tap the menu in the upper-left corner, and find “Subscription group settings” or a similarly named subscription management option. The wording may vary slightly between versions.
- Tap “＋” in the upper-right corner. Enter an easy-to-recognize name in the Remarks field, such as “Work subscription,” paste the full link into the subscription address field, and save.
- Return to the main screen, open the menu in the upper-right corner, and select “Update subscription” or “Update current group subscription.” After adding the address, you still need to update the subscription for the nodes to appear in the list.
- Tap a node to select it, then tap the connect button in the lower-right corner. The first time you connect, Android will display a VPN connection request. Confirm it to allow the app to handle the relevant traffic.
- Use the client’s connection test feature, then open the website you actually need to access and verify it works. Latency test results are for reference only and don’t guarantee that a website will be accessible.
If you have a single node link, copy it and choose an option such as “Import from clipboard” rather than entering it in the subscription address field. Free nodes provided on this site should also be imported according to the link type specified on the page. Whether they work depends on the actual connection results.
3. Troubleshooting subscription updates and connection failures
- No nodes appear after an update: Check that the link is complete and doesn’t contain extra spaces, line breaks, or Chinese punctuation. Ask the provider to confirm that the subscription hasn’t expired.
- The update times out: First, make sure your phone has internet access. Then check whether the subscription domain is accessible, following the provider’s instructions. If necessary, switch between Wi-Fi and mobile data and try again.
- Nodes appear but won’t connect: Update the subscription and try a different node. Check that your system clock is set to sync automatically, and make sure no other VPN app is running at the same time.
- The connection succeeds, but some apps won’t open: Check the routing mode and per-app proxy settings, and make sure the target app hasn’t been excluded. During testing, change only one setting at a time to make it easier to identify the cause.
4. How team use relates to account environment stability
Adding the same subscription does not mean everyone uses the same exit IP. The source of traffic seen by a website may change depending on the selected node, changes to the node’s backend, or network switching. Account platforms may also assess risk based on the device, login location, and activity, so a subscription should not be treated as a tool for “account stability.”
Teams can standardize client versions and instructions, clarify node groups and permitted uses for members, and avoid switching regions without a specific reason. For work accounts, prioritize the platform’s member permissions and security verification features, and don’t share account passwords. If an account triggers an unusual verification request, follow the platform’s instructions rather than repeatedly switching nodes and attempting to log in.
First confirm that the subscription updated successfully, then check the node connection, and finally review the app settings. This can reduce repeated troubleshooting. Free nodes shouldn’t be the sole network connection for critical business operations. Always comply with local laws and regulations and the relevant terms of service.