This article addresses how to add a subscription in v2rayNG and why, when used by a team, some people can connect while others disconnect, or why node lists may differ. It is suitable for users who need to distribute subscription links uniformly to colleagues, family members, or small teams. Just follow the steps to complete import, update, and basic troubleshooting.
1. Standard steps for adding a v2rayNG subscription
v2rayNG is a commonly used V2Ray/VLESS/VMess client on Android. A subscription bundles multiple nodes into a single link for convenient centralized updates. Before adding it, make sure what you received is a subscription URL, not an individual vmess:// or vless:// node link.
- Install and open v2rayNG on your Android phone. It is recommended to download the latest client from a trusted source.
- Tap the “+” in the top right corner or the menu button, then select “Subscription settings.”
- Tap “Add subscription.” For the note, you can enter an easily recognizable name such as “Team Subscription” or “freevpn-x Nodes.”
- Paste the subscription link into the address bar, save it, and return to the main screen.
- Open the menu in the top right corner, tap “Update subscription,” and wait for the node list to refresh.
- Select a node and tap the connect button in the bottom right corner. On first use, allow VPN permission when prompted.
If the list is empty after updating, it is usually because the link was copied incompletely, the subscription has expired, or the current network cannot access the subscription URL. Try switching between Wi-Fi and mobile data first, then try again.
2. How are subscriptions and account stability related in team use?
In team scenarios, stability depends not only on a specific node, but also on how the subscription is managed. When multiple people share the same subscription, frequent simultaneous connections or large cross-region network differences may cause different latency or make some nodes unavailable. It is recommended that team members use the same subscription, but each person should choose the node that best suits their own network rather than having everyone crowd onto the same entry point.
In addition, the subscription link is best maintained centrally by an administrator, while members are only responsible for “updating subscriptions” and “switching nodes.” This helps avoid parameter inconsistencies caused by someone manually changing the configuration. If the free nodes provided by this site are used for temporary testing, it is also recommended to confirm connectivity first before using them as a team backup option. Do not treat a single free node as the only long-term exit.
3. Recommended team configuration habits
- Use consistent naming: Clearly indicate the purpose in the subscription note, such as “Office Backup” or “Mobile Network Backup.”
- Update regularly: If the connection is abnormal, tap “Update subscription” first instead of immediately deleting the client.
- Distribute node selection: The same team can agree to prioritize low-latency nodes, but avoid concentrating all devices on a single node.
- Keep a backup subscription: Prepare a backup subscription or free node link so you can switch quickly if the main subscription fails.
4. Connection failure troubleshooting checklist
If v2rayNG still does not work after adding a subscription, troubleshoot in this order: first confirm whether the system time is syncing automatically; then check whether the subscription can update normally; next, long-press a node and run “Test real connection”; finally, switch network environments. If it shows a timeout, the current network may be blocking access or the node may be unavailable. If it shows a configuration error, the subscription content is most likely expired or the client version is too old.
When team members report problems, it is best to provide three pieces of information: the network being used, the node name, and the error message. Based on this information, the administrator can determine whether it is an issue with an individual phone or whether the subscription as a whole is unavailable. This is more efficient than reinstalling repeatedly and also helps improve stability in multi-user environments.