This article addresses “how to import nodes into v2rayNG” and why, after importing, you still may not be able to open websites, your IP does not change, DNS leaks occur, or the browser environment appears abnormal. It is suitable for Android users to complete node import, connection testing, and basic troubleshooting step by step.
1. Preparation: Install v2rayNG and obtain nodes
v2rayNG is a commonly used V2Ray client on Android, supporting common protocols such as VMess, VLESS, Trojan, and Shadowsocks. You first need to install the latest version of v2rayNG from a trusted source, then prepare a node link or subscription URL. This site also compiles testable free nodes. Before using them, it is recommended to copy the full link first to avoid import failures caused by missing characters.
Common node formats include: individual node links starting with vless://, vmess://, trojan://, or ss://; or a subscription URL starting with https://. Single nodes are suitable for temporary use, while subscriptions are better for batch updates.
2. Three ways to import nodes into v2rayNG
- Import from clipboard: Copy the full node link, open v2rayNG, tap the “+” in the upper-right corner, and select “Import from clipboard.” After a successful import, a new configuration will appear in the list.
- Scan a QR code: If the node provides a QR code, tap “+”, select “Scan QR code,” and point the camera at the code to add it.
- Import via subscription: Tap the menu in the upper-left corner, go to “Subscription settings,” add the subscription URL, save it, return to the main screen, then tap the menu in the upper-right corner and select “Update subscription.”
After importing, tap the node name to select it, then tap the round connect button in the lower-right corner. On the first connection, the system will prompt you to create a VPN connection; choose Allow. Once connected successfully, a VPN icon will usually appear in the status bar.
3. Check IP, DNS, and browser environment after connecting
Many people assume that once connected, everything will work, but you still need to check three things: IP, DNS, and browser. First, open an IP lookup website and confirm whether the exit IP has changed to the node’s region. If the IP has not changed, the node may not be selected, VPN permission may not have been granted, or the connection may have been interrupted by the system’s battery-saving policy.
Next, check DNS. If DNS still shows your local ISP, DNS poisoning or privacy leaks may occur. In v2rayNG’s “Settings,” you can enable remote DNS or use the built-in DNS-related options; menu names may vary slightly by version. Regular users do not need to change complex parameters—use the default recommended values first, and switch DNS modes only if problems occur.
Finally, check the browser environment. It is recommended to test in an incognito window and disable extensions that may affect the proxy. If some websites still detect your original region, the cause may be a combination of browser cache, logged-in account region, cookies, and WebRTC leaks. You can clear site data or switch to another browser and test again.
4. Troubleshooting import failures and connection issues
- If a format error appears: check whether the link is complete, especially the ending parameters and whether the name after the hash sign has been truncated.
- If the subscription update is empty: confirm that the subscription URL can be opened in a browser, or try again later, as free nodes may have expired.
- If it connects but webpages will not open: switch to another node, check whether the system time is accurate, and try changing networks.
- If only some apps work: check in v2rayNG settings whether per-app proxy is enabled; if necessary, change it to global proxy.
- If the connection disconnects frequently: disable battery-saving restrictions on the phone and allow v2rayNG to run in the background.
If you just want to get started quickly, the recommended process is: copy the subscription URL, import it into v2rayNG, update the subscription, choose a node with lower latency, then check IP and DNS after connecting. If you run into problems, switch nodes first, then check browser cache and system VPN permissions. This will cover most cases where “it imported successfully but still doesn’t work.”