This guide explains how to add a v2rayNG subscription. Follow the steps to install the client, enter a subscription link, update nodes, and test the connection. For teams, it also explains how subscriptions, exit IPs, and account environment stability are related, so you don’t attribute every login issue to a node.
1. Before you start: Check the installation package and subscription type
v2rayNG is an Android client. Download the installation package from the project’s official GitHub Releases page, and avoid modified versions from unknown sources. During the first installation, you may need to allow your browser or file manager to install apps. We recommend disabling this permission afterward.
Have the subscription address provided by your service provider ready. It is usually an HTTPS link. A subscription link is not the same as a link to an individual node: content starting with vless://, vmess://, and similar prefixes should generally be imported via the clipboard. Clash-specific subscriptions may not be recognized directly by v2rayNG, so choose a subscription labeled as compatible with v2rayNG or V2Ray whenever possible.
2. Steps to add a subscription in v2rayNG
- Open v2rayNG and go to “Subscription group settings” in the side menu. The name or location may vary slightly between versions.
- Tap the plus button to add a subscription. Enter a note such as “Personal” or “Team backup,” paste the full subscription link in the 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.” Wait for the node list to appear.
- Select a node, then tap the connect button at the bottom. The first time you connect, Android will ask for permission to set up a VPN connection. Confirm to allow the app to route network traffic.
- Run the in-app connection test, then open a browser to check whether websites load. A successful latency test does not mean every website will be accessible, so check access directly.
After saving a subscription, you still need to update it; otherwise, the main screen may show no nodes. Updating usually refreshes the configuration but does not mean you are connected. Check the client’s status and verify access in practice.
3. Troubleshooting import or connection failures
- Update fails: Check that the link was copied in full and contains no extra spaces or line breaks. Confirm that the subscription has not expired or been reset. If your current network cannot reach the subscription address, try again on a trusted network.
- The list is empty after updating: Make sure you did not enter the service provider’s website address by mistake, and ask the provider whether the subscription is compatible with v2rayNG.
- A node is listed but you cannot connect: Try another node, check that your phone’s time is set to sync automatically, and make sure no other VPN app is running at the same time.
- Some apps won’t open: Check the routing mode, per-app proxy settings, and DNS settings. Restore the default configuration before testing, and avoid changing several settings at once.
4. How does team use affect account environment stability?
A subscription is simply a way to update node configurations. Adding a subscription does not, by itself, make an account environment more stable. The login experience can also be affected by frequent changes to the exit IP, device and browser state, logins from multiple locations, and the target platform’s security rules. Even a fixed node may get a new exit IP after a server-side change, so it cannot guarantee that an account will not be asked to verify its identity.
Teams should use individually authorized accounts and subscriptions, keep a record of primary and backup nodes, and avoid unnecessary switching. If prompted to verify a login, follow the platform’s instructions rather than repeatedly switching nodes and trying again. Treat subscription links as credentials; do not share them in public group chats, screenshots, or documents. If you use free nodes listed on this site, start with basic connectivity tests. For sensitive tasks, choose a connection solution from a trusted source with clear access permissions, and comply with local laws and platform rules.