This guide explains how to import nodes into v2rayNG, and how to troubleshoot problems such as websites still not loading after import, an incorrect IP address, DNS leaks, or browser environment issues. It’s intended for Android users who want to import nodes, update subscriptions, and perform basic troubleshooting step by step.
1. Before you begin
v2rayNG is a popular V2Ray/Xray client for Android. It supports node links such as vmess, vless, and trojan, as well as subscription URLs. Before you start, make sure you’ve installed the latest version of v2rayNG and obtained your nodes from a trusted source. This site provides some free nodes for testing, but free nodes can stop working quickly, so test the latency and connectivity soon after importing them.
- Single node: Usually a long link that starts with vmess://, vless://, or trojan://.
- Subscription link: Usually a URL that starts with https:// and contains multiple nodes.
- QR code: An image encoding node information that you can scan to import directly.
2. Three ways to import nodes into v2rayNG
- Import from clipboard: Copy the complete node link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” The new node will appear in the list.
- Import by scanning a QR code: Tap “+” in the upper-right corner, select “Scan QR code,” and scan the node’s QR code. Make sure to grant camera permission.
- Import a subscription: Tap the menu in the upper-left corner, open “Subscription settings,” tap “+” to add the subscription URL, and save it. Return to the main screen and select “Update subscription” from the menu.
Once the import is complete, select a node and tap the connect button in the lower-right corner. The first time you connect, you’ll see a VPN permission prompt; tap Allow. When the status shows connected, open a browser and visit a test website.
3. What IP, DNS, and your browser environment affect
Importing a node successfully doesn’t necessarily mean you can access websites normally. Your IP, DNS, and browser environment also matter. After connecting, the public IP shown when you visit a website should be the node’s exit IP. If you still see your local carrier’s IP, the proxy may not be working, or the app may not be routing traffic through the VPN.
DNS translates domain names into IP addresses. Incorrect DNS settings can cause problems such as connecting successfully but being unable to open websites, resolving to the wrong address, or DNS leaks. In v2rayNG settings, you can use built-in DNS or remote DNS. Avoid running other accelerators that also take over DNS.
Your browser environment can also affect the results. For example, browser cache, extensions, WebRTC, and saved account region information can all lead websites to flag unusual activity. When troubleshooting, try incognito mode and disable unnecessary extensions. For a cleaner test, try another browser.
4. Common troubleshooting steps for connection failures
- Imported node isn’t working: Long-press the node, select “Test real connection,” or try another node.
- Subscription update failed: Check that the subscription URL is complete and that your network can access it.
- It shows connected, but you can’t access the internet: Switch nodes, restart v2rayNG, or check whether another VPN is enabled on your phone.
- Some apps aren’t using the proxy: Check that the app hasn’t been excluded from v2rayNG’s per-app proxy settings.
- Websites won’t open in the browser, but apps work normally: Clear the browser cache, disable proxy-related extensions, and test in an incognito window.
If you’re unsure what’s causing the problem, try these steps in order: update the subscription, switch nodes, test your IP, check DNS, and try another browser. This will help you quickly determine whether the node has stopped working, the client is misconfigured, or the issue is caused by your browser environment.
5. Usage tips
Free nodes are suitable for temporary testing and light use, but their stability depends on the number of users and the status of the connection. For everyday use, keep several working nodes and update your subscription regularly. After importing a node, avoid changing protocol parameters unless you know exactly what the server requires. Most users only need to import the node, select it, and connect.