This article answers the question “How do I add a subscription in v2rayNG?” It walks you through installing the client on an Android phone, importing and updating a subscription, and testing the connection. It also explains how node switching relates to account environment stability when used by a team. Adding a subscription only retrieves node configurations; it does not guarantee greater account stability or replace any identity verification required by a platform.
1. Before you begin: Check the client and subscription link
Download the Android installation package suitable for your device from the official v2rayNG project release page. Avoid modified versions from unknown sources. After installation, have the subscription link provided by your service provider ready. If this site’s free nodes page offers a subscription, first confirm that its format is compatible with v2rayNG.
A subscription link is not the same as a link to a single node: subscriptions are generally used to retrieve and update multiple nodes, while links to individual nodes often begin with protocol prefixes such as vless:// or vmess://. Do not use the URL of a purchase or information page as the subscription address. Subscription links may contain access credentials, so don’t post them in public group chats or include them in screenshots.
2. How to add a subscription in v2rayNG: Follow these steps
- Copy the complete subscription link and check that no spaces, line breaks, or punctuation from a chat message have been included at either end.
- Open v2rayNG and look in the side menu for “Subscription group settings” or a similar option. The wording may vary slightly between versions.
- Tap the add button, enter a descriptive label such as “Team work subscription,” paste the link into the subscription address field, and save.
- Return to the node list and select “Update subscription” or “Update current group subscription” from the menu. Wait for the update to finish, then confirm that nodes appear in the list.
- Select a node and tap the connect button. The first time you connect, allow Android to create a VPN connection.
- First run the client’s connection test, then open a frequently used website to check whether it loads. If the test succeeds but the website won’t open, check your routing, DNS, and system network settings.
Saving a subscription does not mean the nodes have been updated. If the list is empty after saving, run an update and check the message. If the first fetch fails, try switching between Wi-Fi and mobile data. If the subscription address requires an existing proxy to access, ask the provider how to retrieve it.
3. Using subscriptions as a team: How to reduce account environment fluctuations
A subscription itself does not directly determine whether a business account remains stable. The actual factors include the selected node’s exit IP, region, and network quality, as well as the login device and usage patterns. Frequently switching between regions may trigger unfamiliar-login alerts or additional verification on some platforms, but sticking to one node does not guarantee that you will avoid security checks.
We recommend assigning each team member or device a regular node and avoiding unnecessary changes of region. Don’t repeatedly change exit points during critical tasks. If a switch is necessary, make sure the connection is working before continuing. Teams should use collaboration accounts and permission controls allowed by the platform; don’t share accounts or switch networks to bypass platform restrictions.
4. Troubleshooting subscription update failures or connection problems
- Update error: Check that the link is complete and hasn’t expired, and confirm whether the provider has changed the subscription address.
- No nodes after importing: Check that you haven’t used a webpage URL by mistake, and that the current version supports the subscription format and protocols.
- Nodes appear but won’t connect: Try another node in the same group and check that your device’s clock is accurate.
- Some apps behave unexpectedly after connecting: Check the per-app proxy and routing settings to confirm that the target app is using the proxy.
- Frequent disconnections: Check Android’s battery optimization and background restrictions to prevent the system from closing the client.
When troubleshooting, change only one setting at a time and record error messages and test results. If you contact the provider for help, you can share the client version, network type, and redacted logs. Do not send the complete subscription address, password, or token.