This article explains how to add a subscription in v2rayNG. Follow the steps to install the client, paste in the subscription address, update the nodes, and test the connection. It also explains how teams can reduce account login issues caused by frequent node switching when sharing a subscription. Successfully importing a subscription does not mean your exit IP is fixed; account environment stability also depends on the node’s exit IP, the device, and the platform’s own rules.
1. What to prepare before adding a subscription
v2rayNG is primarily for Android. Download the installation package from the project’s official release channel, and avoid modified versions from unknown sources. If installation fails, first check system compatibility and the package architecture. Menu names may vary slightly between versions, so follow the labels shown in your app.
Prepare a valid subscription address, usually a complete link starting with https://. This differs from a single vless:// or vmess:// node link: a subscription address retrieves and updates configurations in bulk, while a single-node link is usually imported from the clipboard. When copying, make sure not to include spaces, line breaks, or extra text added by a messaging app.
2. How to add a subscription in v2rayNG
- Open v2rayNG and find “Subscription Group Settings” or a similar option in the side menu.
- Tap the plus button to create a group. Enter an easy-to-recognize name in “Remarks,” such as “Team Daily Use,” paste the complete subscription link into the address field, and save.
- Return to the configuration list, open the menu in the upper-right corner, and select “Update Subscription” or “Update Current Group Subscription.” After adding a subscription, you’ll usually need to update it manually; saving the address alone does not automatically add nodes.
- Wait for the nodes to appear in the list, select one, and tap the connect button. The first time you connect, allow the VPN connection when prompted by the system.
- Open a browser and visit the target website to confirm that the connection works. You can also use the client’s connection test as a guide, but don’t assume a node is working properly based on latency alone.
Keep subscription links secure, like sensitive credentials. Don’t put them in public documents or share screenshots showing the complete address. When using free nodes from sources such as freevpn-x.com, check the update time and usage instructions first; availability can change at any time.
3. How team use relates to account environment stability
A subscription is simply a way to distribute node configurations; it does not automatically provide a fixed exit IP. Different nodes in the same subscription may be located in different regions, and a node’s exit IP may change even if its name stays the same. Frequently switching regions while logged in may trigger verification on some platforms, but not all account security issues should be attributed to VPN use.
- Agree on a preferred region and backup nodes for team members. When handling tasks on the same account, avoid switching back and forth whenever possible.
- Each person should use their own authorized account and device. Prefer the platform’s official team-member features; don’t share passwords or bypass platform restrictions.
- After updating the subscription, check the currently selected node and make sure it hasn’t switched to another region before continuing with important tasks.
- If your work requires a fixed exit IP, ask the service provider whether this is supported. Don’t treat free public nodes as a fixed-IP service.
4. What to do if the subscription update fails or you can’t connect
If you see an “Update failed” message, first check that the link is complete and hasn’t expired, then confirm that your current network can access the subscription address. If needed, switch between Wi-Fi and mobile data and try again; some subscription sources may require a working proxy to update. Don’t submit private subscription links to untrusted online conversion tools.
If the nodes have been imported but you still can’t access the internet, try another node in the same group, then check that your phone’s date and time are set to update automatically, no other VPN is active, and the client isn’t outdated. A successful node test doesn’t mean all apps are using the proxy. Check the routing mode and per-app settings as well. When troubleshooting as a team, record the error message, client version, and node region. Before sharing screenshots, be sure to hide subscription addresses and node credentials.