This article explains how to add a subscription in v2rayNG, covering each step from installing the client and entering the subscription URL to updating nodes and testing the connection. It also explains how changing exit IPs can affect account environment stability when a subscription is shared across a team. This guide is for Android phones; menu names may vary slightly between versions, so refer to the interface on your device.
1. Before You Add a Subscription: Check the App and Subscription URL
Get an installation package for your phone from the official v2rayNG project release page, and avoid modified versions from unknown sources. After installing the app, prepare the subscription link provided by your service provider, which usually starts with https://. Unlike individual vless:// or vmess:// node links, a subscription retrieves and updates multiple configurations at once. Individual links are generally imported from the clipboard.
Treat your subscription link like a password: don’t post it in public group chats, screenshots, or support tickets. Before using a subscription as a team, also confirm that the provider allows multiple users and check for device or simultaneous connection limits.
2. How to Add a Subscription in v2rayNG
- Open v2rayNG, go to the side menu, and find “Subscription settings” or a similarly named option.
- Tap the add button. Enter an easy-to-recognize name in the remarks field, such as “Team daily,” then paste the full subscription link into the address field.
- Check that no spaces, line breaks, or Chinese punctuation have been added to the beginning or end of the link. Save it and return to the main screen.
- Open the main screen menu and select “Update subscription” or “Update current group subscription.” When the update finishes, check that the node list contains configurations.
- Select a node, then tap the connect button. The first time you connect, Android will display a VPN connection request. Approve it to establish the local VPN tunnel.
- Open a browser and visit a website you need to use, then check that your target apps can connect to the internet. When you’re done, disconnect if you no longer need the proxy.
Saving a subscription URL does not complete the import; you must update the subscription. If the app already contains other configurations, make sure you’ve selected the right group so you don’t mistake an active subscription for one that hasn’t taken effect.
3. What to Do If a Subscription Update Fails or You Can’t Connect
- Update fails: First check that your phone has internet access, then verify that the link is complete and the subscription has not expired or been reset. Avoid refreshing repeatedly in quick succession.
- Update succeeds, but no nodes appear: Check whether the subscription content is compatible with the client. If necessary, ask the provider for a URL intended for v2rayNG.
- Nodes appear, but you can’t connect: Try another node in the same subscription, check that your system date and time are set to sync automatically, and temporarily disable other VPN apps before trying again.
- Some apps stop working after connecting: Check the routing mode and per-app proxy settings, and make sure the target app is not excluded. Don’t assume every website is accessible based on latency tests alone.
If the issue persists, note the error message, client version, and time the problem occurred, then contact the provider for help. Before sharing logs, redact sensitive information such as the subscription URL and account identifiers.
4. How Team Use Relates to Account Environment Stability
Adding a subscription only retrieves configurations; it does not guarantee a fixed exit IP. Different nodes in the same subscription may use different regions or exit IPs, and an exit IP may change even if the node name stays the same. Frequently switching regions or sharing the same service account among multiple people may trigger additional verification from the platform. However, account security checks also depend on the device, login activity, and the platform’s policies.
Your team can agree on which nodes members should use by default and when to switch. If a problem occurs, record it before making changes, and avoid having multiple people repeatedly attempt to sign in. For important services, keep a recovery method available and enable multi-factor authentication. This site’s free nodes are suitable for learning and temporary testing, but should not be relied on to keep critical business operations stable.