This article explains how to import nodes into v2rayNG, and why your IP, DNS, and browser environment can still affect things after importing. It’s intended for first-time users configuring V2Ray/VLESS/VMess nodes on an Android phone. Follow the steps to connect and troubleshoot basic issues.
1. Before you import
First, install v2rayNG on your Android phone. We recommend getting it from a trusted app store, GitHub Release, or a well-known open-source mirror. After installing it, prepare your node information. It usually comes in one of three forms: a subscription link, a QR code, or a single vmess/vless/trojan link. This site provides free nodes for testing and subscription links, but free nodes can be unstable, so it’s a good idea to have a few backups.
- Subscription link: Usually starts with http or https and can import multiple nodes at once.
- QR code: Convenient for importing from a webpage or another device.
- Clipboard link: Copy the full node link, then import it in the client.
2. Three ways to import nodes into v2rayNG
- Import from a subscription: Open v2rayNG, tap “+” in the upper-right corner, and choose “Subscription settings” or “Import subscription from clipboard.” Paste the subscription address and save it. Return to the main screen, tap the menu in the upper-right corner, and select “Update subscription.” Once the update is complete, the nodes will appear in the list.
- Import by scanning a QR code: Tap “+” in the upper-right corner and choose “Scan QR code.” Grant camera permission, then point the camera at the node’s QR code. Once recognized, the node will be added to the list automatically. If scanning fails, increase your screen brightness or copy and import the link instead.
- Import from the clipboard: First, copy a link such as vmess://, vless://, or trojan://. Return to v2rayNG, tap “+,” and select “Import from clipboard.” If the link is reported as invalid, check that it wasn’t truncated by your messaging app.
After importing, select a node and tap the circular start button in the lower-right corner. The first time you connect, a VPN connection request will appear; tap Allow. A key icon at the top of the screen means the proxy is handling your phone’s traffic.
3. How your IP, DNS, and browser environment are related
Successfully importing a node doesn’t guarantee that everything will work. Once connected, your public-facing IP address changes to the node server’s IP. If your local IP is still displayed, you may not have started the proxy, may have selected the wrong routing mode, or the app may not be routing traffic through the VPN. DNS translates domain names into IP addresses. DNS issues can result in being connected but unable to open websites. In v2rayNG settings, enable remote DNS or use the client’s recommended default option to avoid leaking DNS requests to your local network.
Your browser environment can also affect the results. Some browsers have proxy extensions installed, use secure DNS, or have cached an old page, which can make websites behave unexpectedly even when your phone is connected. Try testing in a private window or switching browsers; if needed, clear the browser’s DNS cache or other cached data. Don’t rely on just one website for testing—try a search engine, a video site, and an IP lookup page.
4. Common troubleshooting steps for connection failures
- Empty subscription: Check whether the subscription address has expired and whether you copied the entire link.
- Node timeout: Switch to another node. Free nodes are often unstable during peak hours.
- Incorrect system time: An inaccurate phone clock can cause a TLS handshake to fail. Enable automatic time setting.
- Unable to resolve domain names: Try changing the DNS settings or restart v2rayNG before reconnecting.
- Only some apps don’t work: Check per-app proxy settings, LAN bypass, and routing mode.
If you just want to get started quickly, importing from a subscription is the best option because it makes future node updates easier. For a quick, one-off test, scanning a QR code or importing from the clipboard is faster. When troubleshooting, check in this order: “Is the node valid? Is the VPN running? Has the IP changed? Is DNS working? Is the browser using cached data?” This is the most efficient way to find the problem.