This article explains how to import nodes into v2rayNG. It covers three methods—pasting a link, scanning a QR code, and updating a subscription—and how to tell whether connection problems are caused by the node, IP, DNS, or browser settings. It is intended for Android users. Menu names may vary slightly between versions, so follow the labels in your app.
1. What to prepare before importing
Install the client from the official v2rayNG project release page or another trusted source to avoid modified versions from unknown sources. Prepare a node sharing link, QR code, or subscription URL, and allow the app to access the network. Common sharing links start with vmess://, vless://, or trojan://. Subscription URLs are usually HTTPS links, but not every web address can be used as a subscription.
Sharing links and subscription URLs may contain access credentials. Don’t post screenshots publicly or submit them to unfamiliar websites for parsing. If you use this site’s free nodes, check the protocol type, last updated time, and usage instructions first. Whether a node connects successfully can only be confirmed by testing it.
2. How to import using the three methods
- Import from clipboard: Copy a complete node sharing link, open v2rayNG, tap “+” in the upper-right corner, then select “Import config from clipboard.” Check the list to confirm the configuration was added, then tap it to select it. If you see a message saying no valid configuration was found, check that the beginning of the link wasn’t omitted and that no explanatory text or line breaks were copied with it.
- Scan a QR code: Tap the scan option under “+” and grant camera permission when prompted. Position the entire QR code within the frame. If the QR code is saved on your device, check whether the scanning screen supports loading it from your gallery. If not, display the code on another device and scan it.
- Import multiple nodes through a subscription: Open “Subscription settings” or a similar option in the side menu, add a subscription, enter a recognizable name, and paste the subscription URL. Save it, return to the configuration list, and select “Update subscription” from the menu. Saving the URL alone won’t generate any nodes; after the update succeeds, select a configuration from the list.
If a subscription update fails, first check that the URL is complete and hasn’t expired, and that your current network can reach the subscription service. If your version has a “Update via proxy” option, it usually requires an existing working connection. You don’t need to select it when importing for the first time.
3. How to connect and verify the import
Select a node and tap the connect button. The first time you connect, Android will display a VPN connection request; confirm it to continue. You generally shouldn’t run another VPN at the same time. If there’s a conflict, close any other apps using the system VPN connection first. Then use the client’s connection test and open a frequently used website to verify access. A latency test can help with troubleshooting, but it doesn’t guarantee that all websites will work.
4. How to troubleshoot IP, DNS, and browser settings
Importing successfully doesn’t mean the connection is working. Importing only saves the settings. An inactive node, network restrictions, or mismatched parameters can still prevent access. First try another trusted node and check that your system time is set automatically. Don’t change the server address, port, or TLS parameters in the link without a good reason.
Your exit IP depends on the active connection and routing rules. Direct and proxied traffic may show different IP addresses, so don’t draw conclusions based on a single lookup page. If the client shows a normal connection but a website reports a DNS resolution error, check your DNS settings. It’s best to restore the client’s default settings and avoid applying changes from multiple DNS tools at once.
If the issue occurs only in one browser, compare it with an incognito window or another browser, and check extensions, cache, Secure DNS, and any separate proxy settings. Troubleshoot in this order: “Update subscription—switch nodes—test connection—check DNS—check browser.” Change only one setting at a time to make it easier to identify the cause.