This article explains how to import nodes into v2rayNG. It covers three methods on Android—importing a single-node link, a subscription URL, or a QR code—then explains how to connect and what IP, DNS, and browser settings can affect. Menu names may vary by version, so follow the options shown in your app.
1. Install the client and prepare your node details
Download the installation package from the official v2rayNG GitHub releases page. Avoid installing modified versions from unknown sources. If Android warns that installs from this source aren’t allowed, temporarily enable installation permission for the app you used to download the package, then turn it off when installation is complete. Have the node link, subscription URL, or QR code provided by your service provider ready. You can also use the free nodes on this site for testing, but you’ll need to verify that they work.
A single-node link is not the same as a subscription URL. Links beginning with vmess://, vless://, trojan://, and similar prefixes are usually node links. A URL beginning with https:// could be a subscription or just a webpage, so check the provider’s instructions. Subscription URLs may contain access credentials, so don’t share them publicly.
2. Choose an import method based on what you have
- Import a copied link: Copy the complete node link, open v2rayNG, tap “＋” in the upper-right corner, and select “Import config from clipboard.” Return to the home screen and check that the new configuration appears in the list. Make sure the copied text doesn’t include extra instructions or omit any characters at the end.
- Add a subscription: Open “Subscription group settings” or a similar option in the menu, create a group, and enter a recognizable name. Paste the subscription URL into the URL field and save it. Return to the home screen, then select “Update subscription” or “Update current group subscription” from the menu. Wait for the nodes to appear. Saving the URL alone does not fetch the nodes.
- Scan a QR code: Tap “＋,” select the scan option, grant camera access, and point the camera at the node’s QR code. If the image is saved on your device, check whether the scanning screen supports importing from your photo library. If not, display the QR code on another device and scan it.
3. Connect and confirm that it’s working
Select a node on the home screen, then tap the start button. The first time you connect, Android will prompt you to authorize the VPN connection. Confirm, then check for a VPN icon in the status bar. Avoid running another app that uses the system VPN at the same time, as this may cause a conflict.
Try opening a regular webpage first, then visit the site you want to check. You can also use a trusted IP lookup page to see your outbound IP address. Successfully importing a node doesn’t guarantee that the connection will work. Latency tests are only a guide; actual browsing results are what matter. To route traffic from browsers and other apps through the client, check the per-app proxy settings and make sure the apps you want to use haven’t been excluded. Routing rules may still send some traffic directly.
4. Troubleshoot connection issues in order
- No configuration was imported: Check that the link is complete, that you haven’t copied a regular webpage instead of a subscription URL, and that your version supports the protocol.
- Subscription update failed: Make sure the URL hasn’t expired and your device’s date and time are correct. Try switching between Wi-Fi and mobile data. If needed, ask the provider whether a particular network environment is required.
- The VPN icon is visible, but webpages won’t load: Try another node and check for VPN conflicts, per-app proxy settings, and routing mode. Don’t assume you’re connected just because the icon is showing.
- Only certain websites have problems: Check DNS settings and your browser’s Secure DNS setting. Before making temporary changes, note the original values. You can also use a private browsing window to rule out issues with cache, cookies, or extensions.
Your IP address is the network exit point that websites see. DNS resolves domain names, while your browser environment includes information such as cookies, language, and time zone. All three can affect what you see, but switching nodes won’t automatically clear your login state or guarantee that every website will show the same region. When troubleshooting, change one setting at a time and test the result before moving on. This helps avoid mistaking a browser issue for a node problem.