This guide explains how to add a subscription in v2rayNG: install the client, enter the subscription URL, update the node list, and connect. It also covers what to check if your IP address doesn’t change after connecting, webpages won’t load, or you need to troubleshoot DNS and browser settings. Menu names may vary slightly between versions, so refer to the labels in your app.
1. What to prepare before adding a subscription
Download the Android installation package from a trusted source, such as the official v2rayNG project releases page, and choose the version that matches your phone’s processor architecture. If you’re not sure which one to use, check the release notes. Avoid modified versions from unknown sources. You’ll also need the subscription link provided by your service provider, which usually starts with HTTPS. A subscription URL is not a webpage introducing the service or a link for sharing a single node. When copying it, make sure you don’t include spaces, line breaks, or explanatory text.
If this site’s free-node page offers a subscription link, copy it as instructed on the page. Free subscriptions may become unavailable, and adding one successfully doesn’t guarantee that every node will connect. A subscription link may also contain personal credentials, so don’t share screenshots of it or forward it to others.
2. How to add a subscription in v2rayNG
- Open v2rayNG and go to “Subscription Settings” in the side menu, or to the subscription management page with a similar name.
- Tap the plus icon in the upper-right corner. Enter a recognizable name in “Remarks,” such as “Daily subscription.”
- Paste the full subscription link into the “Address” or “URL” field. Check that it’s correct, then save it. If there’s an enable switch, leave it on.
- Return to the main node screen, open the menu in the upper-right corner, and select “Update subscription” or “Update current group subscription.” Wait for the update to finish.
- When the nodes appear in the list, select one and tap the connect button. The first time you connect, allow Android’s VPN connection request.
- Open a familiar webpage to test the connection. If it won’t load, try another node and check the client logs or connection test results.
Saving a subscription and updating it are two separate actions. If you only enter the URL without updating it, the list may remain empty. If you only have a link for a single node that starts with vless://, vmess://, or a similar prefix, use a feature such as “Import from clipboard” on the main screen instead of entering it as a subscription URL.
3. What to check if the update fails or you can’t connect
If the update fails, first check that regular webpages load on your current network. Then make sure the subscription link hasn’t expired, been cut off, or been restricted to logged-in users. If the client supports “Update subscription via proxy,” try it only if you already have a working proxy connection; enabling it may not help if you don’t have a usable node.
If the nodes appear but won’t connect, try switching between Wi-Fi and mobile data, enabling automatic system time, and testing a different node. Pause other VPN apps to avoid conflicts over Android’s VPN connection. Don’t immediately reinstall the app repeatedly or clear all data, as you could lose your settings.
4. How IP address, DNS, and browser settings are related
Seeing “Connected” doesn’t mean that all apps are using the proxy. If your detected public IP address hasn’t changed, check the routing mode and per-app proxy settings. Make sure your current browser isn’t excluded, and check whether the test site is matched by a direct-connection rule. You can temporarily switch to global proxy routing to compare results, then restore your preferred mode afterward.
If some websites won’t load, DNS resolution may be involved, but this alone isn’t enough to conclude that there’s a DNS leak. Leave the client’s default settings in place to start, then check Android Private DNS, your browser’s Secure DNS, and the client’s DNS settings one at a time. Changing several settings at once can make the problem harder to pinpoint.
Finally, retest in a browser incognito window to rule out effects from the cache, cookies, or extensions. A website’s displayed language or account region may not change when your public IP address changes, so these aren’t reliable indicators that the proxy has failed. Checking in this order—subscription update, node connection, routing scope, DNS, and browser—usually makes it easier to find the problem.