This guide addresses the common question, “What should I do if v2rayNG won’t connect?” It’s aimed at users who are just getting started with V2Ray/VLESS nodes. In many cases, the app itself isn’t broken—the issue may be with the node details, your phone’s network, system permissions, or an outdated subscription. Follow the steps below to identify the cause of most connection failures.
1. Check that the node is available
After opening v2rayNG, don’t keep tapping Connect. First, check the status of the current node. Long-press the node and select “Test current configuration for a real connection” or a similar test option. If the test times out or reports a handshake failure or TLS error, the node may be inactive, the configuration may be incomplete, or your network may be unable to reach the server.
- If you’re using a subscription link, tap the menu in the upper-right corner and select “Update subscription” first.
- If you imported a vmess, vless, or trojan link manually, make sure no characters were left out when copying it.
- Try two or three different nodes from the same subscription instead of judging it by a single node.
- This site compiles free node resources, but their stability can vary with the number of users. We recommend keeping several backup nodes available.
2. Check your phone’s network
If the node seems fine, check your phone’s network next. Close v2rayNG and open a regular domestic website in your browser to confirm that your phone can access the internet. Then switch between Wi-Fi and mobile data and test again. Some public Wi-Fi, campus networks, and corporate networks restrict proxy connections.
- Close v2rayNG and make sure regular webpages open.
- Switch between Wi-Fi, 4G, and 5G, then reconnect to the node.
- Turn off battery saver and data saver to prevent the system from blocking background connections.
- If you use two SIM cards, try switching the default card for mobile data.
Also note that some phones show a prompt asking you to grant VPN permission. If you accidentally tapped Deny, v2rayNG won’t be able to establish a local VPN tunnel. Go to your system settings, find VPN or app permissions, remove the old VPN configuration, and try connecting again.
3. Check v2rayNG’s basic settings
A common mistake for beginners is misconfiguring the routing mode, DNS, or proxy settings. In most cases, you can leave the default settings as they are; we don’t recommend changing complex routing rules right away. In v2rayNG’s settings, make sure options such as “Enable local DNS” and “Per-app proxy” haven’t been misconfigured.
If you want only certain apps to use the proxy, make sure the target apps are selected under Per-app proxy. If you’re not sure, turn off Per-app proxy and test using global mode first. Once it works, you can adjust the rules as needed. If Google or YouTube won’t open but domestic websites work, you can also try switching the routing mode to “Bypass LAN and mainland addresses” or a similar option.
4. Identify the cause from the error message
- Connection timed out: Often caused by an unreachable node, network restrictions, or a blocked port. Try a different network or node.
- TLS handshake failed: Often caused by mismatched domain, SNI, or TLS settings. Reimporting the subscription is usually the safest option.
- EOF / connection reset: The node may be congested or interrupted, or the protocol may not match. Try another node.
- Connected, but webpages won’t open: Check your routing, DNS, per-app proxy settings, and whether your browser has an additional proxy configured.
5. Recommended troubleshooting steps for beginners
The quickest approach is to troubleshoot in this order: node, network, permissions, then settings. First update your subscription and try another node, then switch your phone’s network. Next, confirm that VPN permission is allowed. Finally, restore v2rayNG’s default settings and reimport the configuration. Avoid changing many options at once, or it’ll be difficult to tell which change fixed the problem.
In short, there’s rarely just one reason v2rayNG won’t connect. For beginners, first make sure the node comes from a reliable source, the subscription is up to date, and the phone’s network is working. Then check DNS and routing settings. Following the steps in this guide should help you determine whether the issue is with the node, the network, or the client configuration.