This guide explains how to add a v2rayNG subscription. It walks you through installing the Android client, importing a subscription, updating nodes, and checking the connection. It also explains why switching nodes can affect account environment stability when used by a team. Adding a subscription only retrieves node configurations; it does not guarantee that the connection will work or prevent third-party accounts from triggering security checks.
1. Before you begin: Install the client and verify the link
Download an installation package for your device from the official v2rayNG GitHub Releases page. Avoid modified versions from unknown sources. If installation requires you to allow your browser to install apps, grant permission temporarily for that source only, then turn it off once installation is complete. Menu names may vary slightly between versions; the steps below use the typical interface.
Get the subscription link from your service provider. It usually starts with HTTPS. Unlike a single vmess:// or vless:// node link, a subscription lets you retrieve and update configurations in one place. A subscription URL may contain a personal token, so don’t share it in group chats, public documents, or screenshots. If you’re using it as a team, first make sure your provider allows sharing.
2. How to add a v2rayNG subscription: Follow these steps
- Open v2rayNG, open the side menu, and find “Subscription group settings” or a similarly named subscription management option.
- Tap the “+” in the upper-right corner. Enter an easy-to-recognize name in the remarks field, such as “Work backup.” Paste the full subscription URL into the URL field, check for spaces or line breaks at either end, then save.
- Return to the configuration list, open the menu in the upper-right corner, and select “Update subscription” or “Update current group subscription.” Wait for the update to finish, then check whether nodes appear in the list.
- Select a node and tap the connect button in the lower-right corner. If Android displays a VPN connection request for the first time, confirm that the app is from a trusted source, then allow the connection.
- Use the client’s connection test or open the target website to check whether the connection works. Latency tests can offer a useful indication, but actual access is the best measure.
After saving a subscription, you still need to update it; otherwise, the list may remain empty. If you have a link for a single node, use an import option such as “Import from clipboard” instead of entering it as a subscription URL.
3. Team use: How subscriptions relate to account environment stability
A subscription does not keep an account environment fixed. The selected node, exit IP, network quality, device, and login behavior are what affect access. After a subscription update, a node with the same name may use a different exit IP, so the same node name does not mean the exit IP has stayed the same.
Teams can standardize their client version and procedures, but they don’t need to share the same private subscription. For important work, use a dedicated device and a relatively consistent, reliable node where possible. Avoid having multiple people sign in to the same account at once or switching regions frequently in a short period. If you’re prompted to verify your account after changing nodes, follow the platform’s instructions rather than retrying repeatedly. These practices can reduce changes in the account environment, but they do not replace the platform’s account security rules.
4. Troubleshooting failed updates or connection issues
- Update error: First check that your phone can connect to the internet, the link is complete, and the subscription has not expired. If you see a certificate error, correct your device’s system time; do not simply disable certificate verification.
- No nodes after updating: Make sure you updated the correct group, and ask your provider to confirm that the returned content is compatible with v2rayNG.
- Nodes are listed, but you can’t access anything: Try another node, check whether another VPN is using the connection, and review any error messages in the client logs.
- Only some apps are affected: Check per-app proxy settings and routing rules to make sure the target app hasn’t been excluded. Avoid changing multiple settings at once.
When testing a free subscription, keep a working configuration available as well. This site’s free nodes can be used for temporary testing, but availability and exit IPs may change. When asking for help, share only redacted error messages and your client version. Do not publicly share subscription tokens or complete node credentials.