This article addresses the most common question, “How do you import nodes into v2rayNG,” and explains why you still need to pay attention to IP, DNS, and the browser environment after importing. It is suitable for Android users who have just installed v2rayNG and received free nodes or a subscription link but do not know how to use them.
1. What to prepare before importing nodes
v2rayNG is a commonly used V2Ray/VLESS/VMess/Trojan client for Android. It does not provide routes by itself, so you need to import nodes. Nodes usually come in three forms: a single share link, a QR code, or a subscription link. This site organizes testable free node information, and you can also use your own existing provider subscription.
- Make sure the latest version of v2rayNG is installed on your phone.
- Prepare the node link, such as one starting with vless://, vmess://, or trojan://.
- If it is a subscription, it is usually a full https link.
- It is recommended to first close other VPN apps to avoid port conflicts.
2. Three ways to import nodes into v2rayNG
- Import from the clipboard: Copy the node link, open v2rayNG, tap the “+” in the upper-right corner, and select “Import from clipboard.” After importing, the server name will appear in the list; just select it.
- Import by scanning a QR code: If the node page provides a QR code, tap “+” and choose “Scan QR code,” allow camera permission, and point at the QR code to recognize it.
- Import a subscription link: Tap the menu in the upper-left corner, go to “Subscription settings,” tap “+” to add the subscription address, save it, then return to the main screen and choose “Update subscription.” Once the update is complete, multiple nodes will be generated automatically.
After the import is complete, tap the circular button in the lower-right corner to start the connection. On first use, you will be prompted to create a VPN connection; choose Allow. After a successful connection, a VPN icon will usually appear in the status bar.
3. How IP, DNS, and the browser environment are related
Many users assume that once the node is connected, everything is done, but in fact access results also depend on the IP, DNS, and browser cache. The IP determines the exit location seen by the website; DNS is responsible for resolving domain names into IPs; and the browser environment may store old cookies, language, time zone, or cache.
If you still cannot open a website after connecting, first visit an IP lookup page in your browser to confirm whether the exit IP has changed. If the IP has not changed, the proxy has not actually taken effect; if the IP has changed but the website still behaves abnormally, the issue may be with DNS or browser cache.
In v2rayNG, it is recommended to go into Settings and enable “Bypass LAN addresses.” For the routing mode, you can first choose “Global” for testing. DNS can usually be left at the default setting; if domain name resolution fails, you can try switching to the app’s built-in DNS or restarting the network. As for the browser, you can test in an incognito window or clear the target website’s cache.
4. Troubleshooting checklist for connection failures
- Has the node expired or been deleted? Try another node.
- Is the phone’s time accurate? Incorrect time can cause the TLS handshake to fail.
- Was the subscription updated successfully? Update the subscription manually and check for errors.
- Is the network restricted? Switch from Wi-Fi to mobile data for testing.
- Is the protocol supported by the client? Older versions of v2rayNG may not support some newer parameters, so updating is recommended.
If you just want to quickly determine where the problem comes from, the simplest method is this: first import 2–3 different nodes, switch to Global mode, and open an incognito browser to test whether the IP changes. This helps distinguish whether the issue is an invalid node, a DNS problem, or abnormal access caused by the browser environment.
In summary: importing nodes into v2rayNG is not complicated. The key is to distinguish between a “single node” and a “subscription link,” then check the IP, DNS, and browser cache after importing. By following the steps above, ordinary users can generally complete the full process from import to troubleshooting.