This article explains how to add a subscription in v2rayNG, step by step—from copying the subscription link and adding it to updating nodes and testing the connection. It also explains how IP, DNS, and the browser environment can affect the results. This guide is for v2rayNG on Android; menu names may vary slightly between versions, so follow the labels shown in your app.
1. Before you begin: Check the installer and subscription type
Install the client from the official v2rayNG project release page or another trusted source. Avoid modified versions from unknown sources. You’ll need a subscription link that supports v2rayNG, usually one that starts with https://. A single vless://, vmess://, or trojan:// link is generally a node-sharing link. Import it using a feature such as “Import from clipboard” rather than entering it as a subscription address.
Subscription links may contain access credentials. Don’t share screenshots or forward them publicly. If you get a subscription from this site’s free nodes page, check which clients it supports and read the update notes first. Free resources may stop working, so importing one does not guarantee that it will work.
2. How to add a subscription in v2rayNG
- Copy the entire subscription address. Make sure it contains no extra spaces, line breaks, or Chinese punctuation.
- Open v2rayNG and find “Subscription group settings” or a similar option in the side menu.
- Tap the plus button to add a group. Enter an easy-to-recognize name in “Remarks,” paste the link into “Optional address” or “Subscription address,” then save.
- Return to the node list, open the menu in the upper-right corner, and select “Update subscription” or “Update current group subscription.” Adding an address does not automatically download the nodes.
- Once the nodes appear, select one and tap the connect button. When prompted for the first time, allow Android to create a VPN connection.
- Open a browser and visit the target website. If it doesn’t load, try another node and check the client logs if needed.
Saving a subscription and updating it are two separate steps. If the list doesn’t change, first check that you’re viewing the correct group, then see whether an error appeared during the update. To refresh the nodes later, you usually only need to update the subscription—you don’t have to delete and recreate it.
3. Troubleshooting subscription and connection problems
- Update times out: Check that your Wi-Fi or mobile data connection is working, then try switching networks. Some subscription addresses can only be accessed through an existing connection; check with the provider to find out how to retrieve yours.
- Parsing error or no nodes after import: Make sure you have a client subscription, not a webpage address, login page, or configuration intended for another client. Also check whether the subscription has expired.
- Nodes appear but won’t connect: Set the system date and time to automatic, update the client, and try another node. Don’t turn off certificate verification just to clear an error.
- All apps lose internet access after connecting: Check whether another VPN, accelerator, or app that uses the VPN channel is running. Close conflicting tools first.
4. How IP, DNS, and the browser environment are related
Your IP is the network exit address websites see. Whether it changes depends on the routing rules and whether the target app’s traffic goes through the proxy. Per-app proxy settings or bypass rules may leave some apps using your regular network. A successful connection does not mean all traffic is going through the proxy.
DNS translates domain names into addresses. If only some domains fail to load, check the logs for resolution errors and look for conflicts between Android’s Private DNS and the client’s DNS settings. Avoid changing several settings at once. The browser’s Secure DNS, cache, cookies, and login status can also affect access. You can compare results in a private window or another browser, but private browsing does not change your network exit IP.
When troubleshooting, work through these steps in order: “Can the subscription be updated? Can a node connect? Can the target website be accessed?” Change just one setting at a time to make it easier to pinpoint the cause.