This guide explains how to import nodes into v2rayNG and troubleshoot issues that may persist after importing, such as webpages not loading, an unchanged IP address, DNS leaks, or unusual browser behavior. It’s designed to help Android users import nodes, update subscriptions, and perform basic troubleshooting step by step.
1. What to prepare before importing
v2rayNG is a popular Android client for V2Ray, VLESS, and VMess. It doesn’t provide server connections, so you’ll need a node link or subscription URL. Common formats include vmess://, vless://, and trojan://, or a subscription URL. You can use your own nodes or visit the free nodes page on this site, copy a working link, and import it.
Before importing, check that your phone’s time is set to update automatically, your network can access domestic websites, and you’ve installed a recent version of v2rayNG from a trusted source. An incorrect time can cause TLS certificate verification to fail, making it appear that the node is connected even though there’s no internet access.
2. Three ways to import nodes into v2rayNG
- Import from clipboard: Copy a single vmess, vless, or trojan node link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” Once imported, the node will appear in the list.
- Import by scanning a QR code: If the node is displayed as a QR code, tap “+” in the upper-right corner, select “Scan QR code,” grant camera access, and scan the code. This is useful for importing a node from a webpage on your computer to your phone.
- Import a subscription: Tap the menu in the upper-left corner, go to “Subscription settings,” tap “+” to add a subscription URL, and save it. Then return to the main screen and select “Update subscription.” Subscriptions are useful for importing multiple nodes and can be refreshed with one tap.
After importing, select a node and tap the circular button in the lower-right corner to connect. The first time you connect, you’ll see a VPN permission prompt; tap Allow. A key or VPN icon in the status bar indicates that the proxy tunnel is active.
3. How IP, DNS, and browser settings affect your results
Many users assume that a successful connection guarantees access to the sites they want, but your IP address, DNS, and browser settings also matter. Your IP address indicates your external connection’s exit location. Visit an IP lookup site to check whether it shows the node’s location. If it still shows your local carrier’s IP, you may not have started the connection, may have selected the wrong routing mode, or may not have granted the system VPN permission.
DNS resolves domain names. If DNS requests still go through your local network, websites may not load, redirect unexpectedly, or show the wrong region. In v2rayNG, you can enable remote DNS or use the built-in DNS policy in Settings. Most users don’t need to configure anything complex; leave the defaults in place and keep the client up to date.
Your browser settings can also affect the results. Cached data, cookies, location permissions, and WebRTC may reveal your previous location to websites. When testing, use an incognito window and disable website location access. If an account triggers a risk-control check, avoid switching frequently between nodes in different regions.
4. Quick troubleshooting for connection failures
- After importing a node, tap “Test real connection.” If it times out, try another node or update your subscription.
- Make sure your phone’s date and time are set to update automatically to avoid TLS handshake failures.
- If all nodes in the same subscription fail, check whether the subscription URL has expired and whether it was copied in full.
- Turn off other VPNs, accelerators, or private DNS apps to avoid conflicts.
- If the connection works but webpages won’t load, switch to global routing mode for testing, then switch back to split tunneling.
In summary, importing nodes into v2rayNG is straightforward. The key is to copy the correct link, update subscriptions properly, and remember that a connected status doesn’t necessarily mean your browsing environment is working correctly. If you run into problems, check your IP, DNS, and browser cache one by one to identify the cause.