This article explains how to import nodes into v2rayNG. It covers three methods—links, QR codes, and subscriptions—and describes how teams can avoid mistakes and troubleshoot connection failures. A successful import does not guarantee internet access or a stable account environment; you should also check node availability, routing mode, and changes to your exit IP.
1. What to prepare before importing
v2rayNG is an Android client. Download the installation package from a trusted source, such as the project’s official GitHub Releases page. Do not install modified versions from unfamiliar group chats. Have a node share link, QR code, or subscription URL ready. Common links start with vless://, vmess://, trojan://, and similar schemes; subscription URLs usually use HTTPS.
Do not share node links or subscription URLs publicly, as they may contain access credentials. When using free nodes, check their source and last update. Related resources provided on this site can serve as test references, but you should verify their availability yourself.
2. Three import methods: choose based on what you have
- Import from clipboard: Copy the complete node share link, open v2rayNG, tap “+” in the top-right corner, and select “Import from clipboard.” The wording may vary slightly between versions. Return to the list and check that the new configuration appears. Make sure the link was not truncated or copied together with any explanatory text.
- Scan a QR code: Tap “+” and select the QR code scanning option. Grant camera permission and point the camera at the full QR code. If the code is saved in your device’s photo gallery, check whether the scanning screen supports importing images. If not, use a share link instead. Do not upload credentials to unfamiliar QR code scanning websites.
- Add a subscription: Open “Subscription group settings” in the side menu, or an entry with a similar name. Create a group, enter a label, and paste in the subscription URL. After saving, return to the main screen and use the menu to update the subscription. Saving the URL alone will not display all configurations; check the list after the update completes successfully.
3. How to connect and verify the import
Select a configuration from the list and tap the connect button at the bottom. When prompted for the first time, allow Android to establish a VPN connection. Then run the client’s connection test and visit a few everyday websites. A failed latency test does not necessarily mean you have no internet access; make your final assessment based on both website access and the logs.
Start with the default or rule-based routing mode, confirm that basic access works, and then adjust settings as needed. Seeing the VPN icon on your device only means that the local tunnel has started; it does not prove that the remote node is available. If you need to share a screenshot for troubleshooting, hide the address, UUID, password, and full subscription URL.
4. Team use and troubleshooting connection failures
Each team member should install the client themselves and use authorized configurations. Keep a consistent record of the client version, group name, and last update to avoid confusion between different interface versions. Do not share business accounts for convenience or distribute subscription details casually.
Importing a node does not guarantee a stable account environment. Switching nodes can change your exit IP, region, and network reputation, which may prompt some platforms to request additional verification. For routine collaboration, keep your device and usual network consistent, follow platform rules, and do not use a VPN to bypass security checks.
If you cannot connect, check the following in order: whether your device has a working network connection, whether the link is complete, whether the subscription update returned an error, whether system time is set to update automatically, and whether another VPN is interfering. If a subscription fails to download, first disable your current proxy and try again, or ask the provider whether the URL has expired. If the problem persists, check the logs for messages such as timeouts or DNS resolution failures, then test with another configuration that is known to work.