This article explains how to import nodes into v2rayNG and why, when a team shares access, some people have stable connections while others experience frequent disconnects. v2rayNG is an Android client; connection stability depends on node quality, how nodes are imported, subscription updates, account environment, and phone network settings. The steps below are written for everyday users.
1. What to prepare before importing nodes
After installing v2rayNG on your Android phone, you’ll need node details. These usually come in one of three forms: a single share link, a QR code, or a subscription link. This site collects some free nodes for testing, but free nodes can be affected by the number of users online and network congestion, so they’re best for temporary use. For long-term team use, we recommend managing subscription sources centrally so people don’t copy different configurations from various places.
- Single link: Usually starts with vmess://, vless://, trojan://, or ss://.
- QR code: The link above is encoded as a QR code, making it convenient to import in person.
- Subscription link: A URL containing multiple nodes, suitable for keeping everyone’s configuration up to date.
2. Three ways to import nodes into v2rayNG
- Import from the clipboard: Copy the node link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” The new node will appear in the list. Select it, then tap the connect button in the lower-right corner.
- Import from a QR code: In v2rayNG, tap “+” and select “Scan QR code.” Grant camera permission, then scan the code. This is useful when an administrator shares a node QR code in a group chat for members to scan and import.
- Import from a subscription: Tap the menu in the upper-left corner, open “Subscription settings,” add the subscription URL, and save it. Return to the main screen and select “Update subscription.” This is the best option for teams: when nodes change, you only need to update the subscription instead of sending out a batch of new links.
After importing, try the speed test in the upper-right corner or test each node individually. If you can connect but websites won’t load, first check that you’ve granted system VPN permission and that v2rayNG shows as connected at the top.
3. How import methods affect connection stability for teams
For many teams, the problem isn’t that people don’t know how to import nodes; it’s that everyone has imported a different version. Some use old links, some have imported duplicate configurations, and others haven’t updated their subscriptions in a long time. As a result, some people can connect while others can’t. For team use, we recommend using a shared subscription link and agreeing on an update schedule, such as manually updating once before work each day.
Keep account and device environments in mind, too. Different mobile networks, carriers, and system power-saving settings can all affect connections. On Android, background restrictions may cause v2rayNG to disconnect when the screen locks. Office Wi-Fi may also block UDP, proxies, or unusual traffic, so the same node might work on mobile data but not in the office.
4. Quick checklist for troubleshooting connection failures
- Make sure the node was imported correctly: the link prefix, port, UUID, and other details must not be truncated.
- Update the subscription and try again to avoid using expired nodes.
- Switch networks: if Wi-Fi doesn’t work, try 4G/5G, or vice versa.
- Disable battery optimization and allow v2rayNG to run in the background.
- Try a different protocol or route: VLESS, VMess, and Trojan may perform differently on different networks.
- Remove duplicate configurations: keep the nodes generated by the current subscription and delete older ones imported manually.
If several people on the team experience connection failures at the same time, the subscription source or node route is the likely cause. If only one phone is affected, focus on that device’s network, time settings, permissions, and battery settings.
5. Recommended workflow for teams
The administrator should maintain a single subscription URL, which each member imports once. If a node becomes unavailable, have everyone update the subscription first, then test different nodes. Avoid repeatedly sharing individual node links in group chats; otherwise, it becomes difficult to tell who is using the latest configuration. For everyday users, learning how to import and update subscriptions and perform basic troubleshooting will resolve most issues that arise after importing nodes into v2rayNG.