This article explains how to import nodes into v2rayNG and why, when a team shares the app, some people can connect while others cannot. Follow the steps below to import a single node or subscription link on an Android phone. Using a consistent configuration and avoiding duplicate changes can help keep the account environment stable.
1. Before you import
v2rayNG is a popular V2Ray/VLESS client for Android that supports importing vmess, vless, trojan, ss, and other nodes. Before importing, prepare your node details. They usually come in one of three forms: a single share link, a QR code, or a subscription URL. For team use, it’s best for an administrator to distribute the subscription to everyone rather than having each person manually change settings such as the address, port, or TLS parameters.
- Make sure your phone is set to sync the time automatically. An incorrect time can cause TLS handshake failures.
- Get nodes or subscriptions from reliable sources. This site also provides free nodes for testing.
- Team members should use the same version of v2rayNG where possible to reduce issues caused by client differences.
2. Three ways to import nodes into v2rayNG
Open v2rayNG and tap “+” in the top-right corner to see the available import options. Most users should use a subscription first, followed by a QR code; manual entry should be a last resort.
- Import a link from the clipboard: Copy a node link such as vmess://, vless://, or trojan://, open v2rayNG, tap “+” in the top-right corner, and select “Import from clipboard.” The node will appear in the list when the import is complete.
- Scan a QR code: If your administrator sends you a node QR code, tap “+” and select “Scan QR code.” Grant camera access and point the camera at the code. Once it’s recognized, the node will be added to the list automatically.
- Import a subscription URL: Tap the menu in the top-left corner and open “Subscription settings.” Tap “+” to add a subscription name and URL, then save it and return to the home screen. Select “Update subscription” to add the nodes in bulk.
After importing, select a node and tap the circular connection button in the bottom-right corner. The first time you connect, you’ll be prompted to create a VPN connection. Tap Allow. Once connected, a VPN icon will appear in the status bar.
3. How team use affects account environment stability
When multiple people share the same nodes or subscription, stability depends not only on the connection itself but also on how it’s used. For example, if multiple people frequently switch the same account between different locations and networks, the server may impose connection limits. Members who change the transport protocol, camouflage domain, or SNI settings at will can also end up with inconsistent configurations.
We recommend that teams use a “shared subscription, shared instructions, and a small set of test nodes” approach: the administrator updates the subscription URL, while members only need to update the subscription and switch nodes. Don’t forward the same single-node link to everyone without limit, and avoid frequently clearing the configuration and importing it again. For teams that need a reliable connection for work, name nodes by purpose—for example, “Backup,” “Prefer mobile network,” or “Evening peak test”—so members can report issues clearly.
4. Connection troubleshooting checklist
- Tap “Test all configurations for real connection” to see whether all nodes fail or just one.
- If the subscription update fails, check that the subscription URL was copied in full and that your network can access it.
- If you see “TLS,” “handshake,” or “timeout,” try switching networks, then test another node.
- If only one team member is having trouble, have them check their system time and v2rayNG version, and whether another VPN is enabled.
- When reporting an issue to the team, include the node name, network environment, and error message rather than simply saying, “It doesn’t work.”
In short, importing nodes into v2rayNG is straightforward: copy a link or add a subscription, then update it. For team use, the key is to keep configuration sources consistent, minimize individual changes, and establish a simple process for reporting issues. This makes it easier to determine whether a problem lies with the node, the network, or the client configuration—even when testing with free nodes.