This article addresses the common question, “What should I do if v2rayNG won’t connect?” It’s intended for beginners who are just starting to use V2Ray/VLESS nodes. Follow these steps to check your phone’s network, node configuration, subscription updates, client settings, and system restrictions, and quickly determine whether the issue is an inactive node, a network problem, or an incorrect v2rayNG configuration.
1. First, rule out local network issues
Many connection failures aren’t caused by a faulty node; your current network may simply be unable to connect. Don’t keep deleting nodes. Instead, check the following:
- Close v2rayNG and use your browser to visit a domestic website to confirm that your phone has internet access.
- Switch between Wi-Fi and mobile data and test again. Some workplace, campus, or public Wi-Fi networks restrict proxy connections.
- Turn off power-saving mode, data management apps, accelerators, and firewall apps, as they may block v2rayNG.
- Restart your phone’s network connection: turn on Airplane Mode for 10 seconds, then turn it off and reconnect.
If you can’t access domestic websites either, the problem isn’t v2rayNG, so fix your local network first. If only the proxy connection fails, continue troubleshooting below.
2. Check whether your nodes and subscription are working
If v2rayNG shows messages such as “Connection timed out,” “EOF,” or “handshake failed,” common causes include an expired node, a blocked port, or an incomplete configuration. Try the following:
- Long-press the current node and select “Test current configuration connectivity” or “Test all configurations connectivity.”
- If all nodes fail, update your subscription first: tap the menu in the upper-right corner and select “Update subscription.”
- If you imported a node manually, check that the address, port, UUID, transport protocol, TLS, SNI, and other fields are all filled in correctly.
- Try another node. Don’t conclude that the client is the problem after testing just one node.
This site collects free nodes for testing, but their reliability depends on the number of users and network conditions. We recommend keeping several nodes and testing them in rotation.
3. Check the basic v2rayNG settings
If the node appears to be working but you still can’t access websites after connecting, check the client settings. Open the menu in the upper-left corner of v2rayNG and tap “Settings.” Pay particular attention to the following:
- Routing mode: Beginners should select “Bypass LAN and mainland addresses” or use the default rules to avoid issues with all traffic.
- Local DNS: If websites often fail to load by domain name, try enabling or changing the DNS settings.
- Allow connections from LAN: This generally doesn’t need to be enabled for regular phone use. Leaving it on could lead to a misconfiguration.
- Check that the VPN icon appears at the top of your phone’s screen. This indicates that the system’s proxy connection has been established.
If the VPN icon briefly appears and then disappears, v2rayNG may not have VPN permission. Go to your system settings, find VPN or app permissions, remove the old v2rayNG VPN configuration, and grant permission again.
4. Identify the issue from the symptoms
Beginners can narrow down the issue based on what they see: if the “latency test fails,” the node is likely unavailable or the current network is blocking it; if you “can connect but websites won’t open,” the issue is often related to DNS, routing, or your browser cache; if “some apps work but others don’t,” the cause may be split-routing rules or proxy compatibility issues with the apps themselves.
We recommend troubleshooting in this order: switch networks, update your subscription, try another node, and then reinstall the client. Before reinstalling, export any working configurations to avoid losing your subscription link. When downloading v2rayNG, use a trusted source and keep the client up to date, as older versions may not support some newer VLESS, Reality, or transport parameters.
5. What to do if you still can’t connect
If none of the above works, narrow down the problem: Can the same node connect on another phone? Can the same phone connect using other nodes? Can Clash or sing-box connect on the same network? Cross-testing can help determine whether the issue is with the node, network, or client. Avoid repeatedly changing advanced settings you don’t understand. Keeping the configuration clean and checking one thing at a time is usually the fastest approach.