This guide answers the question “What should I do if v2rayNG won’t connect?” and takes you through troubleshooting in order of risk: first check the client and nodes, then test the subscription and system network, and finally see whether switching between Wi-Fi, mobile data, or a hotspot helps. It’s for everyday users who don’t want to deal with complex settings and just want to get connected again as quickly as possible.
1. Start with 5 basic, low-risk checks
If v2rayNG won’t connect, don’t start by repeatedly changing protocol settings. Many issues are actually caused by expired nodes, an incorrect system time, network permissions, or an outdated subscription. Try these steps in order:
- Open v2rayNG and make sure the switch in the upper-right corner is on and that a VPN icon appears in your phone’s status bar.
- Open the node list, long-press the current node, and choose “Test current service connection” or a similar option to check whether a latency result appears.
- Check your phone’s system time. We recommend enabling “Set time automatically” and “Set time zone automatically.” An incorrect time can cause the TLS handshake to fail.
- Make sure v2rayNG has permission to access the internet and run in the background, and that battery-saving mode isn’t restricting it.
- Switch to another node in the same subscription instead of repeatedly reconnecting to just one node.
If a free node from this site doesn’t work after importing it, try updating the subscription before testing again, as free-node availability can vary with network conditions.
2. Check your subscription, node format, and routing mode
If none of your nodes can connect, first check whether the subscription update failed or the configuration was accidentally changed. Open the menu on the left in v2rayNG, select “Subscription settings,” make sure there are no extra spaces in the subscription URL, then tap “Update subscription.” Once it’s updated, return to the home screen, select a new node, and try connecting again.
Routing mode can also affect your experience. If you’re an everyday user, start with the default routing mode and avoid enabling complex routing rules. If you’ve changed options such as “Routing settings,” “Bypass LAN,” or “Domain strategy,” temporarily restore the defaults and test again. For regular internet access through a proxy, keeping the default settings is usually more reliable.
Also check whether the client supports the node’s protocol. v2rayNG typically supports common protocols such as VLESS, VMess, and Trojan, but a damaged subscription or an incomplete copied link can also result in a node that appears to import correctly but won’t connect. If this happens, delete the node and scan the QR code or import the subscription again.
3. When to switch network environments
If you’ve completed the checks above and still see errors such as “Connection timed out,” “TLS handshake failed,” or “Connection test failed,” try switching network environments. This is a low-risk step that doesn’t involve changing the server; it simply helps determine whether your carrier, router, or Wi-Fi is affecting the connection.
- Switch from home Wi-Fi to mobile data, then test the same node.
- Switch from mobile data to another Wi-Fi network, such as one at work, in a shopping mall, or at a friend’s house.
- Use another phone as a hotspot, connect your phone to it, then run v2rayNG again.
- Restart your router, or temporarily disable features such as security filtering and parental controls.
If you can connect over mobile data, the original Wi-Fi or router may be interfering with the connection. If it fails on every network, the node may be down, the subscription may have a problem, or the client may be misconfigured. In that case, try a different set of nodes instead of repeatedly toggling the VPN on and off.
4. What not to do when a connection fails
While troubleshooting, avoid high-risk steps such as deleting your phone’s system network settings, installing unofficial modified clients, enabling proxy chains without a clear reason, or changing low-level parameters. For most users, it’s enough to follow these four steps: update the subscription, switch nodes, restore the defaults, and try another network.
Finally, we recommend keeping 2–3 working nodes from different sources. If you can’t connect, test the node first, then switch networks. This helps you identify the problem quickly and avoid unnecessary changes. If v2rayNG still doesn’t work, try updating to the latest client version or using clients such as Clash or sing-box to check whether the subscription works there.