What should you do if v2rayNG won’t connect? This article troubleshoots the issue in order: check your device first, verify your nodes next, and then try a different network. It helps you distinguish between an expired subscription, permission conflicts, and restrictions on your current network. The steps prioritize reversible changes, so you won’t need to reset your phone or modify server-side settings.
1. First, determine whether the connection failed or only some apps won’t open
After tapping Connect, check whether v2rayNG shows that it’s running and whether the system displays a VPN icon, then try opening two different websites. A VPN icon does not mean the node is connected—it usually only indicates that the local VPN service has started. If only one app can’t access the internet, first check whether it’s excluded from the per-app proxy settings. Don’t rush to delete the node.
2. Complete these five basic checks in order
- Check your basic network connection: Disconnect v2rayNG and make sure regular web pages load. If public Wi-Fi requires a sign-in, complete the sign-in first. Switching nodes usually won’t help if your basic connection isn’t working.
- Check VPN permissions and conflicts: Reconnect and approve the system’s VPN request. Temporarily turn off other VPNs, ad blockers that use a local VPN, or firewalls, then test again. You can restore your original settings afterward.
- Check your node and subscription: Make sure a node is selected. If you use a subscription, update it once and check for errors. A successful subscription update only means the list was retrieved—it doesn’t guarantee that any of its nodes are working. Try a recently updated node for comparison.
- Check the system time and client: Turn on automatic date and time settings. If your version is outdated, update it through the project’s official release channel. Note your existing settings first, and avoid modified versions from unknown sources.
- Check routing and background restrictions: Temporarily select the app’s global proxy mode and test the connection, then switch back to your original mode. If the connection drops after the screen locks, check battery optimization and background-running permissions. You don’t need to disable all system protections to troubleshoot.
3. When should you try a different network?
If basic internet access works, the same node fails to connect repeatedly, and switching nodes doesn’t help, try a side-by-side test using the same node on different networks: keep the node and client settings unchanged, then switch from Wi-Fi to mobile data or try another Wi-Fi network you trust. Be mindful of mobile data usage, and don’t connect to unfamiliar open hotspots.
If the connection works after switching networks, the issue is more likely related to authentication, access policies, DNS, or the connection path on the original network—but one test isn’t enough to confirm the cause. Company, school, and hotel networks may have explicit restrictions. Follow their usage rules and don’t try to bypass network policies. If both networks fail, check the node’s validity and your client settings first rather than repeatedly changing networks.
4. Narrow down the issue using error messages, and avoid making things worse
Check the latest connection entry in the client log: a timeout may indicate an unreachable node or packet loss; a connection refusal may be related to the service status, address, or port; and a certificate error is a reason to check the system time and configuration source. Don’t hide errors by turning off certificate verification, and don’t change transport settings you don’t understand.
Change only one setting at a time and record the result. If you still can’t connect, when asking for help, provide the client version, Android version, network type, and a redacted error message. Don’t share your subscription link, full node link, password, or UUID publicly. If you use a free node from this site, check when it was last updated; free nodes may stop working, and replacing one with a valid configuration from a trusted source is more targeted than reinstalling the app blindly.