This article addresses the common question “What should I do if v2rayNG won’t connect?” and provides a low-risk troubleshooting process for everyday users: check the app, nodes, and system settings first, then determine whether you need to switch between Wi-Fi, mobile data, or another network. Avoid changing settings at random as your first step.
1. Start with basic, low-risk checks
A failed v2rayNG connection doesn’t necessarily mean the node is down. It could also be caused by an incorrect system clock, missing permissions, a subscription update issue, or local network restrictions. Troubleshoot in order, and avoid changing several options at once so you can pinpoint the problem.
- Check that your phone’s time is correct: Go to your system settings and enable “Set time/time zone automatically.” An incorrect clock can cause TLS handshakes to fail.
- Restart v2rayNG: Completely close the app, including in the background, then reopen it and tap the connect button in the lower-right corner.
- Test another node: If you’ve imported multiple VLESS, VMess, or Trojan nodes, try connecting to a different one to see whether only one node is unavailable.
- Update your subscription: On the v2rayNG home screen, tap the menu in the upper-right corner and select “Update subscription.” When it’s finished, select a node again.
- Check VPN permissions: The first time you connect, the system will prompt you to authorize the VPN connection. You must tap Allow. If you accidentally denied permission, try reinstalling the app or clearing its data.
If you’re using free nodes listed on this site, try updating the subscription or importing it again. Free nodes may be temporarily unavailable due to routing changes, congestion, or maintenance.
2. Check whether the network is the problem
If multiple nodes fail to connect, or you see messages such as timeout, handshake failed, or connection refused, your current network may have restrictive policies. Don’t change advanced settings yet; start with a simple comparison test.
- Switch from Wi-Fi to mobile data, then try connecting to the same node.
- Switch from mobile data back to your home Wi-Fi and see whether the connection works again.
- Turn off system power-saving mode, network accelerators, and VPNs used for ad blocking, as they may conflict with v2rayNG.
- If you can’t connect on your company, campus, or hotel Wi-Fi but mobile data works, that network is likely more restrictive about proxy connections.
When should you switch networks? If the same node works over mobile data but not on a particular Wi-Fi network, or all nodes time out on that Wi-Fi network, try switching networks first. If none of your networks work, the problem is more likely related to the nodes, subscription, or client configuration.
3. Check the logs to quickly identify the error
The built-in v2rayNG logs can be very useful. Open the menu in the upper-left corner, go to “Logs” or “Connection logs,” and try connecting again. Then check the last few entries. Common messages include:
- timeout: Often caused by network blocking, an unreachable node, or a congested route. Try another network or node.
- certificate verify failed: Often related to an incorrect system clock or a certificate verification issue. Check the time first.
- invalid user / authentication failed: The node’s account details don’t match. Try importing the subscription again.
- connection refused: The destination server rejected the connection, possibly because the node is temporarily unavailable.
4. Recommended order of safe troubleshooting steps
To reduce the risk of making things worse, try these steps in order: “update subscription—switch nodes—switch networks—check logs—reinstall the client.” Don’t change parameters such as the transport protocol, TLS, SNI, or port unless the node provider specifically instructs you to. If you still can’t connect, back up your subscription link, uninstall the app, install the latest version of v2rayNG, and import your nodes again. This can resolve issues caused by client cache while helping you avoid disrupting settings that were already correct.
In short: If v2rayNG won’t connect, check the basic settings and node status first, then test across different networks. Only prioritize switching networks when the connection fails on one network but works again after you switch to another.