This article addresses the common question “What should I do if v2rayNG won’t connect?” and offers low-risk troubleshooting steps for everyday users. Start by checking your nodes, subscription, device time, and permissions. Then check whether you need to switch between Wi-Fi, mobile data, or another network. Avoid changing advanced settings right away.
1. Start with basic checks that won’t affect your system
If v2rayNG can’t connect, don’t immediately reinstall the app or change complex settings. Most issues are caused by an unavailable node, an outdated subscription, mobile network problems, or an incorrect system time. Try these steps in order:
- Open v2rayNG and make sure the selected node is the right one. Don’t use a node that’s no longer available or has failed a connection test.
- Tap the menu in the upper-right corner and select Update subscription. If you imported the node manually, copy the full link again and reimport it.
- Check your phone’s date, time, and time zone. Turn on “Set time automatically” if possible. An incorrect time can cause TLS connection failures.
- Make sure v2rayNG has permission to access the network. Some Android systems restrict background network access or limit it in battery-saving mode.
- Disconnect, wait 10 seconds, and then reconnect to make sure the previous connection has been fully cleared.
If this site’s free-node page has a new subscription link or individual node link, you can try a different node. Free-node reliability depends on the number of users and the status of the route, so a connection failure doesn’t necessarily mean the client is broken.
2. Use test results to pinpoint the problem
In the v2rayNG node list, you can use “Test current configuration connectivity for all” or a similar test feature. If only one node fails, that node is probably unavailable. If all nodes fail, check your local network or client settings.
- “timeout” or “i/o timeout”: Commonly caused by network blocking, an unreachable node, or poor network quality.
- “TLS handshake failed”: This may be caused by an incorrect device time, incomplete node configuration, or a certificate issue on the server.
- Connection shows as successful, but webpages won’t load: Check whether the system proxy or VPN permission is enabled, or try switching routing modes.
- Subscription update fails: Make sure the subscription link is accessible. If necessary, switch networks and try again.
When troubleshooting, change only one thing at a time so it’s easier to tell what fixed the issue. Don’t change the transport protocol, port, routing, and DNS all at once, or it will be harder to identify the cause.
3. When to switch network environments
If you’ve confirmed that the node is available but still can’t connect over your current Wi-Fi, try a low-risk network switch. Start with the simplest option: turn off Wi-Fi and switch to mobile data, or connect to another Wi-Fi network, such as at home, at work, or through a hotspot. If mobile data works but Wi-Fi doesn’t, the problem is probably with your current broadband connection, router, or local network restrictions.
Switching networks is worth trying if the same nodes work on someone else’s phone, the subscription updates normally but won’t connect, all nodes time out on your current network, or restarting v2rayNG and your phone hasn’t helped. You can try restarting your router, disabling its security filtering, or temporarily using a mobile hotspot to test.
4. Safe steps to take if you still can’t connect
If none of the steps above work, export your current configuration or save a screenshot before clearing invalid nodes from v2rayNG and importing the subscription again. Don’t install unofficial modified clients from untrusted sources or share your subscription link with strangers. You can also test with another client, such as Clash or sing-box, to determine whether the issue is with the node or v2rayNG compatibility.
In short, if v2rayNG won’t connect, try these steps in order: update the subscription, switch nodes, check the device time and permissions, test your current network, and then switch network environments. This approach is low-risk and makes it easier to quickly pinpoint the problem.