This guide explains how to add a v2rayNG subscription, import it on an Android phone, update nodes, and connect for the first time. It also shows how to tell whether a connection failure is caused by the subscription, exit IP, DNS, or browser environment. Menu names may vary slightly between versions, so follow the labels shown in your app.
1. Before you start: Make sure you have a subscription URL
Install v2rayNG from the project’s official release page or another trusted source, then get a subscription link from your service provider. A subscription URL is not a website URL or an individual node link: subscriptions can usually be updated to retrieve a set of configurations, while individual node links often start with vless://, vmess://, or trojan:// and should be imported using the clipboard import feature.
When copying the link, make sure it doesn’t include spaces, line breaks, or explanatory text. Subscription links may contain access tokens, so don’t post them publicly or send them to strangers. If you use free node information from this site, check the update notes as well; free resources may become unavailable.
2. How to add a subscription in v2rayNG
- Open v2rayNG and go to “Subscription group settings” in the side menu, or a similarly named subscription management page.
- Tap the plus icon. Enter a recognizable name in the remarks field, such as “Daily subscription,” paste the full subscription URL into the address field, and save.
- Return to the configuration list, open the menu in the upper-right corner, and select “Update subscription” or “Update current group subscription.” Saving the URL alone usually won’t generate any nodes.
- Wait for the update to finish, then confirm that configurations appear in the list. If an error appears, check the message first; there’s no need to repeatedly add the same subscription.
- Select a node and tap the connect button. The first time you connect, allow the VPN connection request from Android.
- Test a website you commonly use. If it doesn’t load, try another node and check the connection status or logs in the app.
A successful subscription update and a successful node connection are two different things. The former only means the configuration was downloaded; the latter also depends on the node’s status, your current network, and configuration compatibility. Future updates generally use the existing subscription, so you don’t need to add it again each time.
3. What to do if the subscription won’t update or you can’t connect
- Invalid address message: Copy the original link again and check that it hasn’t been truncated, expired, or replaced with a website URL by mistake.
- Download timeout: Make sure your phone can access the internet, then test using both Wi-Fi and mobile data. If the subscription URL itself is unreachable, follow the provider’s instructions rather than changing the link arbitrarily.
- Parsing failed or no nodes found: The response may not be in a compatible format, or the app version may be outdated. Check the subscription type and update the client from a trusted source.
- Nodes are listed, but you can’t access anything: Try another node, check that your system time is set automatically, and close other VPN apps to avoid conflicts.
4. How IP, DNS, and your browser environment are related
Importing a subscription retrieves configuration files; it doesn’t directly change your browser’s language, time zone, or login status. After connecting, whether your exit IP changes depends on whether your traffic is routed through the proxy. With split-tunneling rules, different websites may use different routes, so you can’t judge all your traffic based on just one website.
DNS resolves domain names. If some domains won’t load, try switching networks, reconnecting, and checking the logs first. Then refer to the documentation for your current version before changing DNS settings, rather than copying unfamiliar parameters. Browser cache, extensions, and website account status can also affect access, so compare results in a private window or another browser.
Change only one setting at a time while troubleshooting. Check whether the subscription updates, then whether the node connects, and finally whether websites load. This makes it easier to pinpoint the problem than changing DNS, routing, and browser settings all at once.