This article explains how to import nodes into v2rayNG, from installing the app to importing via a link, QR code, or subscription, and troubleshooting connection failures. Follow the steps in order. For team use, we also explain how switching nodes relates to account environment stability, so you don’t mistake a successful import for a fixed exit IP.
1. What to prepare before importing
v2rayNG is primarily for Android. We recommend downloading the APK from the project’s official GitHub Releases page and choosing the package for your device’s architecture. If you’re not sure which one to choose, check your phone’s processor information first. Don’t install modified versions from unfamiliar group chats. Have a node share link, QR code, or subscription URL ready, and make sure it comes from a trusted source.
Common share links start with vmess://, vless://, or trojan://. Subscription URLs are usually HTTPS links used to fetch multiple configurations at once. A subscription link is effectively an access credential. Don’t post it in public groups or include it in screenshots. The free nodes on this site are suitable for learning and temporary testing, but availability and exit IPs may change.
2. Three ways to import nodes
- Import from the clipboard: Copy the entire share link, open v2rayNG, tap “+” in the upper-right corner, then select “Import from clipboard.” Return to the list and check that the new configuration appears. Make sure you haven’t copied any explanatory text or missed the end of the link.
- Scan a QR code: Tap “+,” select the QR code scanning option, and grant camera access. If the QR code is saved in your phone’s gallery, check whether your version supports scanning from an image. If not, ask the provider to send the original share link.
- Use a subscription URL: Open “Subscription group settings” in the side menu, or a similarly named option. Create a group, enter a recognizable label and the full subscription URL, and save it. Return to the main screen and use the menu to select “Update subscription.” The wording may vary slightly between versions.
After updating the subscription, select a node and tap the connect button. The first time you connect, you’ll need to approve Android’s VPN request. A VPN icon in the status bar only means the service has started; open a webpage as well to verify that it loads properly. Don’t run another VPN at the same time, as this may cause conflicts.
3. Troubleshooting: imported successfully, but can’t connect
- No configuration was created: Check that you copied a complete share link, not a webpage URL, then try again after updating the client.
- Subscription update failed: Check for spaces in the URL, make sure it hasn’t expired, and confirm that your current network can reach the subscription service. Don’t submit private subscriptions to unfamiliar online conversion tools.
- Node timed out: Switch between Wi-Fi and mobile data, then test another node. A latency test result doesn’t guarantee that webpages will load properly.
- Some apps won’t open: Check the routing and per-app proxy settings, and make sure the target app hasn’t been excluded. If needed, temporarily adjust the rules and compare the results.
4. Team use and account environment stability
The import method itself does not make an account environment more stable. What matters is whether the exit IP changes, how often the apparent location switches, and whether the device or login activity seems unusual. Even nodes with the same name aren’t guaranteed to keep the same exit IP. After updating a subscription, check the selected configuration again.
Teams can standardize the client version and instructions, label configurations by purpose, and review the business platform’s usage rules before switching. Don’t switch between multiple regions in quick succession just to deal with a single timeout. If an account security check appears, follow the platform’s official process. A fixed node may reduce some network changes, but it cannot guarantee that an account won’t be challenged or restricted, and it is no substitute for managing member permissions and enabling two-factor authentication.