This article addresses a common question: “How do I import a node into v2rayNG?” It covers three import methods—links, QR codes, and subscriptions—and the order in which to troubleshoot connection failures. For teams using the app, it also explains how to manage subscriptions and changes in exit locations, helping prevent network issues from being mistaken for account problems.
I. Before importing: Install the client and identify the node type
v2rayNG is primarily for Android. Download the installation package from trusted sources, such as the project’s official GitHub Releases. Avoid modified versions from unknown sources. When you launch the app for the first time, Android may ask for permission to establish a VPN connection. The client needs this authorization to route network traffic.
Have the single-node link, QR code, or subscription URL provided by your service provider ready. Single-node links often begin with vless://, vmess://, or trojan://. A subscription URL is usually an HTTPS link used to retrieve and update configurations. A subscription URL acts as an access credential, so don’t share screenshots of it or forward it to group chats.
II. Three import methods: Choose the one that matches what you have
- Import from a copied link: Copy the complete node link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” Return to the configuration list and confirm that the new entry appears. If you’re copying multiple nodes at once, put each one on a separate line and avoid including any explanatory text.
- Scan a QR code: Tap “+,” select the QR code scanner, and allow camera access when prompted. If the QR code is on the same device’s screen, check whether your app version supports scanning it from an image. If not, ask the provider for a text link instead.
- Add a subscription: Find “Subscription group settings” or a similar option in the side menu. Create a group, enter a name that’s easy to recognize and the subscription URL, then save it. Return to the main screen and select “Update subscription” from the menu. Wait for the nodes to appear in the list. Menu names may vary slightly between versions.
Updating a subscription retrieves configurations from a remote source; it does not connect you automatically. If a group appears but contains no nodes after import, check whether you updated the subscription, whether the URL is complete, and whether the subscription has expired.
III. After selecting a node, how to confirm the connection works
Select the node you want to use, tap the connect button, and accept Android’s VPN authorization prompt. First, use the connection test provided by the app, then open a browser and visit your destination website. A successful latency test does not mean every website will be accessible. If a test fails, check the logs and try accessing the site before drawing a conclusion.
Most users can start with the app’s default routing and DNS settings. Avoid changing several settings at once. If only certain apps can’t connect, check whether per-app proxy settings exclude them and whether routing rules send their traffic directly.
IV. If import or connection fails, troubleshoot in this order
- Link not recognized: Copy the full content again, remove extra spaces or quotation marks, and make sure it isn’t just a regular webpage URL.
- Subscription update fails: Check the phone’s internet connection, the subscription’s validity period, and the URL. If needed, contact the provider to confirm whether the link has changed.
- Node imported but won’t connect: Update the client and subscription, then test another working node. Check that the system date and time are set to update automatically.
- Still can’t access anything after connecting: Disconnect other VPN or proxy tools, then test over both Wi-Fi and mobile data. Before sharing logs, hide sensitive information such as addresses and UUIDs.
V. How does team use relate to account environment stability?
A successful import does not guarantee a stable account environment. The exit IP, region, device, and the website’s own security checks can all affect the login experience. Teams can standardize client versions, group names, and troubleshooting procedures, but shouldn’t casually share subscriptions or accounts; confirm that sharing is authorized first. Avoid switching regions frequently within a short period. Free nodes may change and are better suited to temporary use and troubleshooting; they can’t guarantee a fixed exit location or prevent account verification.