This article addresses the common question, “What should I do if v2rayNG won’t connect?” It offers everyday users a low-risk troubleshooting sequence: check the client and nodes first, then see whether switching between Wi-Fi and mobile data or trying another network helps. This avoids making things more complicated by repeatedly reinstalling the app or changing settings at random.
1. First, check for basic configuration issues
Many v2rayNG connection failures don’t mean the node is completely unavailable. They may be caused by a subscription that hasn’t been updated, an incorrect system clock, or the wrong proxy mode. We recommend following the steps below in order and testing after each one. Don’t change too many settings at once.
- Open v2rayNG and go to the subscription settings. Tap “Update subscription,” or copy and import a subscription link again from the free nodes page on this site.
- Check your phone’s system time. We recommend enabling “Set time automatically” and “Set time zone automatically.” A significant time difference can cause a TLS handshake to fail.
- Make sure the connection switch in the top-right corner is on. Then test a webpage after the VPN icon appears in the status bar.
- In the routing list, select “Bypass LAN and mainland China addresses” or “Global” to test and rule out issues with routing rules.
- Try other nodes in the same subscription, preferably recently updated ones, rather than repeatedly testing the same unavailable node.
If you still can’t access anything after trying these steps, continue by checking your network environment. We don’t recommend immediately wiping your phone or reinstalling the operating system.
2. How to tell if you need to switch networks
Switching network environments usually means moving from your current Wi-Fi to mobile data, or testing with another broadband connection or hotspot. This is a low-risk step that doesn’t affect your account, system permissions, or server configuration, and is a good way to check whether your local network is restricting proxy connections.
- If the same node fails on Wi-Fi but works on mobile data, your current Wi-Fi network or broadband connection may be restricting it.
- If all nodes time out on a particular public Wi-Fi network but work over mobile data, the public network may be blocking the relevant ports or protocols.
- If v2rayNG shows as connected but webpages won’t load, and switching networks fixes the issue, DNS, routing, or gateway restrictions may be to blame.
- If neither mobile data nor Wi-Fi works, but other users report that the nodes are available, check the client version, system VPN permissions, or subscription contents.
Before switching networks, we recommend disconnecting v2rayNG. After switching, wait for your phone’s internet connection to stabilize, then reconnect. Avoid repeatedly toggling airplane mode while connected, as this can make it harder to determine the node’s actual status.
3. Low-risk troubleshooting checklist
If you’re not sure where to start, follow this checklist: update the subscription, switch nodes, change the proxy mode, switch networks, restart v2rayNG, and only then consider reinstalling the client. Back up your subscription link before reinstalling so you don’t lose your configuration.
Also note that some security apps, battery-saving modes, or system management apps may restrict VPNs running in the background. In your phone settings, allow v2rayNG to run in the background and disable any battery restrictions for it. Messages such as “connection refused,” “timeout,” and “TLS handshake failed” typically point to an unreachable node, a network timeout, or a certificate, time, or connection issue, respectively. Use the steps above to check each possibility.
In short, try another node first, then switch networks—this is a sensible troubleshooting order. If the connection only fails on a particular Wi-Fi network, there’s no need to keep changing v2rayNG settings. This site provides free nodes you can import and client tutorials, but the stability of free nodes can vary. If you can’t connect, follow the steps in this article to quickly narrow down whether the issue is with the node, the client, or your local network.