This guide explains how to import nodes into v2rayNG. It’s for Android users who want to import free nodes, subscription links, or individual VLESS/VMess/Trojan nodes into v2rayNG. It also covers how to check your IP, DNS, and browser environment after connecting, to avoid issues such as “connected, but webpages won’t load” or “my IP hasn’t changed.”
1. Prepare v2rayNG and your node information
First, install the latest version of v2rayNG on your Android phone. We recommend getting it from a trusted app store or the project’s release page. Nodes may be provided as subscription links, QR codes, or text copied to your clipboard. This site also collects free nodes for testing; keep in mind that their stability can vary.
- Subscription link: Usually a URL starting with https.
- QR code: Commonly used for a single node or a subscription entry.
- Node text: Starts with vless://, vmess://, trojan://, or a similar prefix.
If you have a block of node text, copy it to your phone’s clipboard first. If you have a subscription URL, make sure it contains no extra spaces or line breaks.
2. Three ways to import nodes into v2rayNG
- Import from clipboard: Copy the node link, open v2rayNG, tap “+” in the top-right corner, and select “Import from clipboard.” Once imported, the server name will appear in the list.
- Import by scanning a QR code: Tap “+” in the top-right corner, select “Scan QR code,” and point your camera at the node’s QR code. If camera access is blocked, allow v2rayNG to use the camera in your system settings.
- Import using a subscription: Tap the menu in the top-left corner, go to “Subscription settings,” add and save the subscription URL, then return to the main screen and update the subscription. This is useful for managing multiple nodes at once.
After importing, tap a node to select it, then tap the connect button in the bottom-right corner. The first time you connect, you’ll be prompted to grant VPN permission. Select “Allow.”
3. Check your IP, DNS, and browser environment after connecting
A successful connection doesn’t necessarily mean all traffic is being routed properly. We recommend checking in this order: Open a browser and search for “IP lookup” to confirm whether your exit IP has changed; then visit a few familiar websites to see if they load; finally, check for DNS issues. If your IP hasn’t changed, app-specific proxy settings, routing rules, or VPN permissions may not be configured correctly.
You can check the routing mode in v2rayNG settings. For general use, start with global mode or a common mode that bypasses LAN/mainland addresses. Avoid changing complex rules without a good reason. If websites fail to resolve, try switching networks, restarting v2rayNG, or enabling the relevant built-in DNS option in the client.
4. Common causes of failure and how to troubleshoot them
- Incorrect node format: A character may have been missed when copying, or the QR code may have expired.
- Subscription update failed: Check whether your network can access the subscription URL. If needed, try again over Wi-Fi or mobile data.
- Server timeout: Free nodes may be congested or inactive. Try another node.
- Browser cache interference: Close and reopen the browser, or use private browsing to check your IP.
- System proxy conflicts: Turn off other VPNs, accelerators, or ad-blocking apps, then try again.
If multiple nodes fail to connect, first check that your phone’s date and time are correct, then update v2rayNG to the latest version. If only one node fails, it’s most likely unavailable; there’s no need to keep changing the client settings.
5. Tips for using v2rayNG
After importing nodes, consider renaming working ones—for example, “date-region-protocol”—so they’re easy to find later. If you use a subscription, you can update it periodically, but avoid updating too frequently to prevent hitting limits. Keep in mind that your connection experience depends on node availability, your network provider, the protocol, and your browser environment. For reliable use, choose a trustworthy node source, keep the client up to date, and follow clear troubleshooting steps.