This article explains how to import nodes into v2rayNG. It covers importing via link, QR code, or subscription, and troubleshooting steps for connection failures. For teams, it also explains how switching nodes relates to account environment stability, helping reduce configuration confusion without guaranteeing that accounts will avoid platform verification.
1. Install the client and identify the node type
v2rayNG is an Android client. We recommend downloading the installation package from the project’s official GitHub Releases page and choosing the version that matches your device architecture. If you’re unsure, check the release notes. Don’t install modified versions shared in unfamiliar group chats. If you already have the client installed, back up your configuration before updating.
Before importing, check what you received: links beginning with vmess://, vless://, or trojan:// are usually individual node links; a QR code may contain node details; and an address beginning with https:// could be a subscription or simply a webpage. Use the provider’s instructions to determine whether an address is a subscription. A tutorial page cannot be imported as a subscription. Menu names vary slightly between versions; the steps below use a typical interface.
2. Import a node using a link or QR code
- Copy the complete node link, making sure you don’t omit the protocol prefix or trailing parameters. Don’t include explanatory text, spaces, or line breaks.
- Open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” A new entry will appear in the configuration list if the import succeeds.
- If you have a QR code, tap “+” and select “Scan QR code,” then grant camera permission when prompted. If the QR code is saved in your photo library, check whether the scanner supports recognizing images. If it doesn’t, ask the provider to send the original link.
- Select the node you want, then tap the connect button on the main screen. The first time you connect, Android will ask you to authorize the VPN connection. Confirm, then test whether you can access a webpage.
A successful import only means the client recognized the configuration; it doesn’t mean the node is currently available. If you see a format error, request the original link again. Don’t guess at encryption, transport, or TLS settings.
3. Add and update a subscription
- Open “Subscription settings” or a similar option in the side menu, tap Add, enter a recognizable label and the complete subscription address, then save.
- Return to the configuration list and select “Update subscription” or “Update all subscriptions” from the menu. Wait for the nodes to appear, then select one to connect.
- If the provider changes the nodes later, update the subscription again. If the update fails, first check that the address hasn’t expired and contains no extra characters, then verify that your current network can access the subscription service.
For free nodes on this site, follow the instructions on the relevant page to choose an import method. Availability depends on actual testing. Subscription links may contain access credentials, so don’t post them in public group chats or include them in screenshots.
4. Team use and troubleshooting connection failures
Teams should standardize the client source, update process, and method for recording issues, but they don’t need to share a single private subscription. Account environment stability depends on more than just the node; it is also affected by the device, browser state, exit region, and platform rules. Frequent region switching may lead to additional verification, and using a fixed node doesn’t guarantee a fixed exit IP. Follow platform rules; a proxy cannot guarantee that you’ll avoid risk controls.
- Can’t connect: Make sure a node is selected, allow the VPN connection, and temporarily disable other VPN apps to rule out conflicts.
- Connected, but webpages won’t load: Compare Wi-Fi and mobile data, then test another node. Also check that the device time is set to sync automatically.
- Only some apps have problems: Check routing or per-app proxy settings and make sure the affected app hasn’t been excluded.
- Still not working: Check the client logs and note errors such as timeouts, DNS resolution failures, or handshake errors. Before reporting the issue, hide server addresses, user identifiers, and subscription tokens.
Change only one setting at a time and test before making further adjustments. Changing the node and routing rules simultaneously can make it difficult to identify the cause.