This guide explains how to add a v2rayNG subscription and troubleshoot common issues, such as connection failures, webpages not loading, an incorrect IP address, or DNS errors. It’s for Android users who have just received a subscription link or free node link. Follow the steps below to import it and troubleshoot any problems.
1. How to add a subscription in v2rayNG
v2rayNG is a popular Android client for V2Ray/VLESS/VMess/Trojan. A subscription is usually a URL that lets you update multiple nodes at once. Individual node links may start with vmess://, vless://, or trojan://. Before adding one, make sure your phone’s clock is accurate and your internet connection is working.
- Install and open v2rayNG on your Android phone. Use a recent version to avoid compatibility issues with newer protocol settings.
- Tap the “+” in the upper-right corner or open the menu, then select “Subscription settings.”
- Tap “Add subscription” and enter a name in the “Remarks” field, such as “freevpn-x nodes” or “Backup subscription.”
- Paste the subscription link into the “Address” field. Make sure you haven’t copied any extra spaces, line breaks, or Chinese punctuation.
- Save your changes and return to the main screen. Open the menu in the upper-right corner and tap “Update subscription.”
- Once the nodes appear in the list, select one and tap the connect button in the lower-right corner. The first time you connect, allow the VPN permission request.
If you got a free node from this site, you may see either a subscription link or a link for an individual node. Subscriptions are useful for updating multiple nodes at once; to add a single node, use “Import from clipboard.”
2. How subscriptions, IP, DNS, and your browser environment are related
Many users assume that importing a subscription means they’ll automatically be able to open webpages, but three other factors are involved: IP, DNS, and your browser environment. The subscription only imports node details into the client. Once connected, your phone’s traffic is routed according to the proxy rules.
- IP: After connecting, visit an IP lookup site. It should show the node’s exit IP, not your local carrier’s IP. If it still shows your local IP, you may not be connected, the app may not be using the proxy, or the routing rules may be misconfigured.
- DNS: DNS translates domain names into IP addresses. If the node is connected but webpages say the server can’t be found, the problem may be DNS poisoning, the system’s DNS cache, or the client’s DNS settings.
- Browser environment: Browser cache, cookies, WebRTC, and account region information can all affect what you see. For example, your IP may have changed, but a site may still determine your location based on your account or cookies.
3. Quick troubleshooting for connection failures
Start by testing the node in v2rayNG. A timed-out test doesn’t necessarily mean the subscription is broken. Your current network may be blocking the connection, the node may be temporarily unavailable, or the protocol may be incompatible. Try these steps in order:
- Tap “Update subscription” again and make sure the link hasn’t expired or been cut off.
- Test over both 4G/5G and Wi-Fi to rule out local network restrictions.
- Try connecting to another node rather than testing just one.
- Check your phone’s system time. A significant time discrepancy can cause TLS handshake failures.
- Try enabling or adjusting DNS in the settings. If needed, clear your browser cache before testing again.
- Close other VPNs, accelerators, and proxy apps to avoid port conflicts or VPN permission issues.
If the connection works but webpages won’t load, try changing the routing mode to “Bypass LAN and mainland China addresses,” or switch to global mode temporarily for testing. If global mode works, the problem is probably with the split-routing rules. If it doesn’t, check the node status, subscription details, or local network.
4. Tips for using subscriptions
Don’t share your subscription link publicly. It could be abused and stop working. Free nodes are suitable for occasional browsing and testing client settings, but not for use cases that require high reliability. For regular use, keep at least two subscription sources and update your node list periodically. When something goes wrong, check whether the subscription imported successfully, the node can connect, your IP has changed, DNS is working, and your browser has cached data. This will help you pinpoint most common issues.