How to Import Nodes into v2rayNG: A Guide to Team Use and Stable Account Environments

This article explains how to import nodes into v2rayNG, connect after updating a subscription, and reduce changes in egress IP when using it as a team. A successful import does not mean the connection will work, nor does it guarantee a stable account environment. Follow the steps below to distinguish import errors, unavailable nodes, and issues caused by changes in your egress IP.

1. Before importing: Install the client and identify the link type

v2rayNG is an Android client. We recommend downloading the installation package from the project’s official GitHub releases page to avoid modified versions from unknown sources. After installing it, check what you have: links beginning with vless://, vmess://, or trojan:// are usually individual node links; an address beginning with https:// and labeled for this purpose by the provider may be a subscription link. Import node links and subscription addresses using the appropriate option; don’t treat an ordinary webpage address as a subscription.

If you get a configuration from this site’s free nodes page, copy the entire content without omitting the protocol prefix or trailing parameters. Subscriptions and node links may contain access credentials, so avoid sharing them in public group chats, support tickets, or screenshots.

2. Choose one of three import methods based on what you have

1. Import a single node from the clipboard: Copy the complete node link, open v2rayNG, tap “＋” in the upper-right corner, and select “Import config from clipboard.” Return to the list and check whether the new configuration appears. If you see an error, check for extra spaces, line breaks, or explanatory text.
2. Import by scanning a QR code: Select the QR code scanning option from the “＋” menu and grant camera access, then scan the node’s QR code. If the QR code is saved on your device, check whether the scanning page supports importing it from your photo library; the option may differ between versions.
3. Import multiple nodes from a subscription: Open “Subscription group settings” or a similar option in the side menu, add a group, enter a name that’s easy to recognize, and paste the subscription address. Save, return to the main screen, and update the subscription from the menu. The exact setting name depends on the version you’re using.

If no nodes appear after updating the subscription, first check whether the address is complete, whether it has expired, and whether your current network can reach the subscription service. Some links return configurations in formats intended for other clients and cannot be used directly in v2rayNG, so confirm compatibility with the provider.

3. Connect after importing: Test the connection before signing in

1. Select the node you want to use, then tap the connect button. The first time you connect, Android will display a VPN connection request. Confirm it and check whether the VPN icon appears in the system bar.
2. Run the connection test provided by the client, then open a browser to check whether webpages load. Latency test results are only a guide and cannot replace an actual browsing test.
3. If you need to confirm your egress IP, use an IP lookup page to check your current public IP and region. Note that per-app proxy settings and routing rules may send different apps through different egress IPs.

If the connection fails, first check that your phone’s time is set to sync automatically, then check whether another VPN app is using the connection. Next, update the subscription, try another node, and compare results over Wi-Fi and mobile data. If it still fails, check the logs for messages such as timeouts or resolution failures. Before sharing logs, redact addresses and credentials.

4. How does team use affect account stability?

The import method itself does not determine whether an account environment is stable. Egress IP, region, device, and frequent changes in login behavior are more relevant. Teams can standardize group names and procedures, but shouldn’t assume that multiple people can safely share one account or that sharing a node will prevent platform verification.

We recommend that each team member keep their own subscription and note their usual and backup nodes. Confirm the egress IP before switching, and avoid reconnecting frequently from different regions during work. Platforms may also assess risk based on the device, cookies, and account permissions, so a fixed node cannot guarantee that verification won’t be triggered. Free nodes can be useful for testing, but their availability may change. Verify the connection before important tasks, and follow platform rules and local laws.