This guide explains how to import nodes into v2rayNG. Starting with installing the client, it covers importing via links, QR codes, and subscriptions, and explains why your IP, DNS, and browser environment may show different results after connecting. It is intended for Android users; menu names may vary slightly by version, so refer to the interface on your device.
1. Install the client and check what you have
We recommend downloading the Android package from the official v2rayNG project release page. Avoid modified versions from unknown sources. If installation prompts you to allow apps from this source, grant permission only to the browser or file manager you are currently using. You can turn off the permission after installation.
Before importing, identify the content: items beginning with vmess://, vless://, or trojan:// are usually links for individual nodes. An HTTPS address may be a subscription or simply a sharing webpage, so check the provider’s instructions. Node links and subscription URLs are not interchangeable; do not import a webpage URL as a node.
2. Import an individual node using a link or QR code
- Copy the full link from the node provider’s page. Make sure you don’t include any explanatory text, spaces, or line breaks.
- Open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” The configuration should then appear on the main screen.
- If you have a QR code, choose the QR code scanning option and allow camera access. If the QR code is saved in your photo library, check whether the scanning screen supports importing from an image.
- Select the node you just imported, then tap the connect button. The first time you connect, Android will prompt you to authorize the VPN. Confirm to allow it to handle your traffic.
If you see a format error, copy the original link again and check whether your client version supports the protocol and its parameters. Don’t delete characters from the link, and don’t publicly share the full node details, as they may expose credentials.
3. Import and update nodes in bulk using a subscription
Open “Subscription settings” or a similarly named option in the side menu, add a subscription, enter a recognizable name, and paste the subscription URL. Save it, return to the main screen, and select “Update subscription” from the menu. Wait for the nodes to appear in the list. Saving a subscription does not mean it has been updated; if the list is empty, check the update result first.
Free nodes provided by freevpn-x.com should also be imported in the format specified on the page. Free resources may become unavailable, and subscription updates may overwrite old entries, so back up important configurations first. Subscription URLs may contain access credentials; don’t share them casually.
4. Imported successfully, but webpages won’t load? How to troubleshoot
- Check the connection status and logs first. An imported configuration is only recognized by the app; it doesn’t mean the node is online. Confirm that the system VPN is running, then test another node.
- Check your network and time settings. Switch between Wi-Fi and mobile data, and enable automatic date and time in the system settings. Network restrictions or an incorrect time may cause connection issues.
- Check the routing mode. With split tunneling, some websites connecting directly is normal. You can temporarily switch to global proxy mode for comparison, then restore your usual settings.
- Rule out DNS and browser issues. If the connection is established but domain names won’t load, check for conflicts between the client’s DNS settings, Android Private DNS, and the browser’s Secure DNS. Change one setting at a time and test again.
A changed exit IP does not mean your browser environment has changed completely. Websites may also take cookies, your logged-in account, location permissions, and browser language into account. You can compare results in an incognito window, but it won’t automatically change your exit IP or guarantee anonymity. If something is wrong, troubleshoot in this order: node, network, routing, DNS, and browser. This is more likely to pinpoint the issue than repeatedly reinstalling the app.