This article explains how to import nodes into v2rayNG and why, when a team uses the same service, some people can connect while others experience instability. You’ll learn how to import nodes using links, QR codes, and subscriptions, and how account settings, network conditions, and client configuration affect connection stability.
1. Before you import: Check the node format and how you’ll use it
v2rayNG is a popular Android client for V2Ray/VLESS/VMess/Trojan. Before importing, check what you’ve received: a single node link, a QR code image, or a subscription URL. This site also curates free nodes for temporary learning and connectivity tests. For long-term team use, it’s better to distribute a shared subscription to reduce errors from copying nodes manually.
- Single link: Usually starts with vless://, vmess://, or trojan://.
- QR code: Essentially a node link, convenient for scanning with a phone.
- Subscription URL: A single URL that lets the client automatically fetch multiple nodes.
2. Three ways to import nodes into v2rayNG
- Open v2rayNG and tap “+” in the top-right corner.
- If you have a single link, select “Import from clipboard.” Copy the entire node link first to avoid missing any characters.
- If you have a QR code, select “Scan QR code” and point your camera at the image or a QR code on another device.
- For a subscription, go to “Subscription settings,” tap “+,” enter a name and the subscription URL, then save. Return to the main screen, open the menu in the top-right corner, and select “Update subscription.”
- After importing, select a node and tap the connect button in the bottom-right corner. The first time you connect, allow VPN access when prompted.
Once connected, open a browser and visit a familiar website to test the connection. If it won’t load, don’t delete the node right away. First, try another node from the same subscription, then check your device’s network connection and system time.
3. For teams: How account and device settings affect stability
When team members use the same set of nodes, stability depends not only on the nodes themselves but also on each person’s device, network, and usage habits. A common issue is that a connection works on office Wi-Fi but fails on mobile data. Or one phone connects while another drops out because of system proxy settings, Private DNS, or battery-saving restrictions.
To make troubleshooting easier, teams should standardize three things: First, use the same subscription URL instead of repeatedly sharing individual nodes in a group chat. Second, label subscriptions clearly by purpose, such as “Android backup” or “Preferred for mobile data.” Third, ask members not to change fields such as the transport protocol, SNI, or TLS settings. For most users, if it works after import, don’t change the advanced settings—changing them by mistake can cause connection failures.
4. Connection troubleshooting checklist
- Update the subscription first: The nodes may have changed, and an outdated configuration may time out.
- Switch networks: Test on mobile data instead of Wi-Fi, or vice versa.
- Check the time: An incorrect phone clock can affect the TLS handshake.
- Close conflicting apps: Another VPN, proxy, or accelerator may be using the system VPN channel.
- Check the routing mode: Beginners should use the default routing mode and avoid switching to global or bypass rules without a reason.
- Restart v2rayNG: Disconnect, fully close the app in the background, and reconnect.
If only a few people on the team are having trouble, first check their phone settings, network permissions, and whether they imported an outdated subscription. If most people fail at the same time, the issue is more likely with the nodes or subscription source. With these steps, you can import nodes into v2rayNG on your own and quickly pinpoint causes of instability when working with a team.