This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow this checklist to check your phone’s network, system time, node details, subscription updates, and app settings. It can help you quickly identify whether the problem lies with your local environment, an inactive node, or an incomplete configuration import.
1. Check your phone’s network environment first
Many connection failures aren’t caused by a problem with v2rayNG itself. Your phone’s current network may simply be unsuitable for establishing a proxy connection. Try these checks in order:
- Switch networks: Toggle between Wi-Fi and mobile data. Some public Wi-Fi networks restrict proxy connections.
- Turn off other VPNs: Android usually allows only one VPN tunnel at a time, so first disable any other accelerators, corporate VPNs, or security apps.
- Check the time: Open your system settings and enable “Set time automatically” and “Set time zone automatically.” An incorrect time can cause TLS handshakes to fail.
- Check permissions: Make sure v2rayNG is allowed to create a VPN connection. When prompted for VPN permission on first launch, don’t tap Cancel.
- Disable battery restrictions: Add v2rayNG to the battery optimization whitelist to prevent the system from killing it in the background.
If everything looks fine, move on to checking your nodes and subscription.
2. Check that your node details are valid
v2rayNG supports protocols such as VLESS, VMess, Trojan, and Shadowsocks. If it won’t connect, long-press the current node and check that its configuration is complete. Pay particular attention to the address, port, UUID, transport, TLS, security type, and SNI fields. If even one of these doesn’t match the server, the connection may time out or fail.
If you imported the nodes from a subscription, tap the menu in the top-right corner and select “Update subscription.” If the node list is empty after the update, the subscription link may have expired, your network may not be able to access the subscription URL, or you may have missed a character when copying it. This site also collects free nodes you can use for testing and comparison. Keep in mind that free nodes can be unstable, so it’s best not to rely on just one.
3. How to interpret common v2rayNG errors
- timeout: Usually means the node is unreachable, the network is blocking the connection, or the port is restricted. Try a different network or node.
- connection refused: The target port refused the connection. This often means the node is inactive or the port is incorrect.
- tls handshake failed: Check that the system time, TLS setting, SNI, and fingerprint settings match.
- no route: The routing rules may be misconfigured. Switch back to the default routing mode to test.
Don’t change too many settings at once. Change one setting at a time and test before moving on; otherwise, it’s difficult to pinpoint the cause.
4. Recommended troubleshooting steps
- Open v2rayNG, stop the current connection, and try connecting to a different node.
- Update the subscription and confirm that the node list refreshes correctly.
- Temporarily change the routing setting to “Bypass LAN and mainland China addresses” or the default rules.
- Open your Android system settings and turn off Private DNS, as some DNS configurations can interfere with name resolution.
- Close v2rayNG from the background, reopen it, and grant VPN permission.
- If it still fails, import the same subscription into a Clash or sing-box client and test it to determine whether the problem is with the client or the node.
Finally, if none of the nodes connect but your browser can access domestic websites, the subscription may have expired or all the nodes may be unavailable. If no VPN app can start, the cause is more likely to be a system permission issue, network restriction, or security app blocking the connection. Work through this checklist to identify the main cause of v2rayNG connection failures.