This article answers the common question, “How do I import nodes into v2rayNG?” Whether you have a single vmess/vless/trojan link or a subscription URL, follow the steps below to import it into v2rayNG on Android. You’ll also learn how it relates to your IP, DNS, and browser environment, which can help you troubleshoot connection failures and websites that won’t load.
1. What to prepare before importing
First, install v2rayNG on your Android phone. We recommend getting the latest version from a trusted source. Then prepare your node details. They usually come in one of three forms: a single link beginning with vless://, vmess://, or trojan://; a subscription URL; or a QR code. This site also provides free test nodes for temporary use and troubleshooting, but keep in mind that their reliability can vary with the number of users.
- Make sure your phone’s clock is accurate. An incorrect time zone can cause TLS handshake failures.
- Check that your network is working. Turn off the proxy first and try visiting a regular website.
- When copying a node, make sure you don’t include extra spaces or explanatory text, and check for unexpected line breaks.
2. Three ways to import nodes into v2rayNG
- Import from the clipboard: Copy the complete node link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” The node name will appear in the list. Select it, then tap the circular button in the lower-right corner to connect.
- Import by scanning a QR code: If the node comes with a QR code, tap “+” and select “Scan QR code.” Grant camera permission and point your camera at the code to add the node. This is a convenient way to import a node from a page on your computer to your phone.
- Import a subscription: Tap the menu in the upper-left corner, open “Subscription settings,” and tap “+” to add the subscription URL. Save it, return to the main screen, and select “Update subscription.” Subscriptions make it easy to manage multiple nodes at once—you only need to update them later.
After importing, start by testing a node with low latency and a clear name. If you’re connected but have no internet access, long-press the node and check that its settings are complete—for example, that the address, port, user ID, transport method, and TLS/SNI fields aren’t blank.
3. How IP, DNS, and the browser environment are related
Once v2rayNG connects, websites will generally see the proxy’s exit IP rather than your local ISP IP. You can visit an IP lookup website to check whether it has changed. If it hasn’t, the VPN switch may be off, the node may not have connected successfully, or the app may not be routing traffic through the system proxy.
DNS affects how domain names are resolved. If you can connect but some websites won’t load, try enabling routing or changing the DNS strategy in v2rayNG’s settings. You can also clear your browser cache to prevent old DNS results from interfering. The browser environment includes cookies, cache, WebRTC, language, and time zone settings. These don’t determine whether a node can be imported, but they can affect how websites identify you. For example, if your IP has changed but your browser still shows an old login location, that’s normal.
4. Quick troubleshooting for connection failures
- Tap “Test all configurations for a real connection.” If it times out, switch nodes or update the subscription.
- Check whether the subscription URL opens normally. An expired subscription can’t update your nodes.
- Turn off battery saver mode and allow v2rayNG to run in the background.
- Switch between Wi-Fi and mobile data to rule out restrictions on your current network.
- If only your browser won’t load pages, try another browser or clear the DNS cache and browser cache.
In summary, the most common ways to import nodes into v2rayNG are using the clipboard, scanning a QR code, and importing a subscription. Subscriptions are the easiest option for most users and require the least maintenance. If something goes wrong, check in this order: “Is the node valid? Is the VPN connected? Has the IP changed? Are DNS or browser cache issues involved?” This should help you identify most problems.