This article explains how to import nodes into v2rayNG. It covers three methods—pasting a link, scanning a QR code, and adding a subscription—and explains how to connect after importing, as well as why your IP, DNS, and browser environment can affect access results. It is intended for Android users; menu names may vary slightly between versions.
1. Check what you have before importing
Install the client from the official v2rayNG project releases page or another trusted source, and grant permissions as prompted when you first launch it. Node details generally fall into two categories: links starting with vless://, vmess://, trojan://, and similar prefixes are single-node sharing links; links starting with https:// may be subscription URLs or just web pages, so check the provider’s instructions.
Single-node links and subscription URLs use different import options. Free nodes provided by freevpn-x.com should also be imported according to the type indicated on the page. Availability can change, and a successful import does not guarantee a connection. Don’t share private subscription links publicly, as they may contain access credentials.
2. Choose an import method based on the information you have
- Import a copied link: Copy the entire node sharing link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” Check the list to confirm the configuration appears. If parsing fails, make sure the link doesn’t contain extra explanatory text or spaces, and that no characters are missing.
- Scan a QR code: Tap the scan option under “+” and grant camera access, then scan the node’s QR code. If the code is saved in your phone’s photo gallery, check whether the scanner supports reading from an image. If not, use the original link or display the QR code on another device.
- Add a subscription: Open “Subscription group settings” or a similarly named option in the sidebar, add a group, enter a label and the complete subscription URL, and save. Return to the main screen and select “Update subscription” from the menu. Saving the URL alone won’t add any nodes.
If the list is empty after updating the subscription, first make sure the URL is still valid and that its response is compatible with v2rayNG. Clash YAML configurations aren’t guaranteed to import directly, so don’t assume any configuration file can be used as a subscription.
3. Connect and verify after importing
Select a node from the list, then tap the connect button. The first time, Android will show a VPN connection request; approve it, then check for the VPN icon in the system status bar and the connection status in the client. Before testing, pause any other VPNs or apps using the VPN connection to avoid conflicts.
Once connected, open a regular web page, then visit a site that requires a proxy, and use a trusted IP lookup page to check your exit IP. With split tunneling enabled, different sites may use different routes, so seeing your local IP on one page doesn’t necessarily mean the proxy isn’t working. To troubleshoot, you can temporarily switch to global proxy mode, then restore your usual settings when you’re done.
4. Imported successfully but can’t access sites? Troubleshoot in this order
- Check the node first: Make sure the configuration is selected and your device’s time is correct, then try another trusted node. A failed latency test can be a useful clue, but it alone doesn’t prove that all access is unavailable.
- Check your network next: Switch between Wi-Fi and mobile data. If a subscription update fails, check whether the subscription URL is accessible on your current network.
- Check DNS: If the logs show a domain resolution failure, check the client’s DNS settings and whether Android’s “Private DNS” is causing a conflict. Change one setting at a time and test again; don’t blindly copy unfamiliar settings.
- Finally, check your browser: Try an incognito window, clear data for the site, and check the browser’s Secure DNS settings. Your sign-in status, cookies, and location permissions can also affect how a site identifies your region.
The node determines the proxy exit, DNS resolves domain names, and the browser retains login and site environment information. These three are related, but they aren’t interchangeable. If the issue persists, check the client logs. Before reporting it, redact the node address, UUID, and subscription token.