This article explains how to import nodes into v2rayNG and troubleshoot common issues after importing, such as webpages not loading, your IP not changing, DNS leaks, or your browser still reporting a location mismatch. Follow the steps below to import nodes, test your connection, and perform basic troubleshooting on an Android phone. This guide is suitable for first-time v2rayNG users.
1. What to prepare before importing nodes
v2rayNG is a popular Android client for V2Ray/VLESS/VMess/Trojan. It does not provide servers, so you’ll need a node link or subscription URL. Node links usually begin with vmess://, vless://, or trojan://. A subscription is an https link containing multiple nodes. This site compiles free nodes for testing, or you can use a subscription you already have.
- Make sure you have the latest version of v2rayNG installed. We recommend downloading it from a trusted app store or the project’s release page.
- Prepare a node link, QR code, or subscription URL.
- Close any other VPN or proxy apps to avoid port conflicts or routing issues.
2. Three ways to import nodes into v2rayNG
Open v2rayNG and tap the “+” button in the upper-right corner to see the available import methods. The most common options are importing from the clipboard, scanning a QR code, and importing a subscription.
- Import from the clipboard: Copy the complete node link, return to v2rayNG, tap “+” and select “Import from clipboard.” The import is successful when the new node appears in the list.
- Scan a QR code: Tap “+” and select “Scan QR code,” then point your camera at the node’s QR code. Once scanned, the node will be added automatically.
- Import a subscription: Open the menu in the upper-left corner, select “Subscription settings,” add and save the subscription URL, then return to the main screen and select “Update subscription.”
After importing, select a node and tap the circular button in the lower-right corner to connect. The first time you connect, Android will ask you to authorize the VPN connection. Tap Allow. Once connected, you’ll usually see a key or VPN icon in the status bar.
3. How your IP, DNS, and browser environment are related after connecting
A successful connection doesn’t necessarily mean you can access every website. It also depends on whether your IP, DNS, and browser environment are consistent. Your IP tells websites where you appear to be connecting from. DNS translates domain names into server addresses. Your browser environment includes details such as language, time zone, cache, cookies, and WebRTC.
After connecting to a node, visit an IP lookup website to check whether your exit IP has changed. If it hasn’t, the proxy may not be routing your traffic. Check whether v2rayNG’s “Routing mode” is set to Global or Rule-based proxy. If webpages load slowly or some domains won’t open, there may be a DNS resolution issue. Try enabling remote DNS in settings or using the client’s default DNS. If a platform still reports a location mismatch, clear your browser cookies, disable WebRTC to prevent leaks, or switch to a node that better matches your account’s region.
4. How to troubleshoot import failures and connection issues
- Format error: Make sure the link was copied in full, including the protocol at the beginning and all parameters at the end.
- Subscription update returns no nodes: Make sure the subscription URL is accessible and isn’t a login page, shortened link, or expired URL.
- Connected but no internet access: Switch to another node or change the routing mode to “Global” for testing.
- Only the browser isn’t working: Check whether a proxy is configured separately in the browser. Try private browsing or a different browser.
- Frequent disconnections: Disable battery restrictions, allow v2rayNG to run in the background, and try a different network.
In summary, importing nodes into v2rayNG is straightforward: copy a node link or subscription, import it, update the subscription if needed, select a node, and authorize the connection. The factors that most often affect your experience are node availability, DNS resolution, and your browser’s cached environment. If you run into problems, check whether your IP has changed, whether DNS is working, and whether your browser is retaining outdated settings. These three steps will usually help you identify the cause quickly.