This article addresses the common question “What should I do if v2rayNG won’t connect?” If you’ve imported a V2Ray/VLESS node but your phone shows a timeout, a TLS handshake failure, inaccessible websites, or a failed latency test, follow the steps below to troubleshoot your network, node, and client settings.
1. First, check whether the problem is with your local network
Many connection failures aren’t caused by a faulty node. They may be due to an issue with your current Wi-Fi or mobile network, or with your system proxy settings. Start by ruling out problems with your local environment.
- Close v2rayNG and open a browser directly to confirm that regular websites load.
- Switch between Wi-Fi and mobile data—for example, switch from your home Wi-Fi to 4G/5G—and try again.
- Restart your phone’s network connection: turn on Airplane Mode for 10 seconds, then turn it off and reconnect.
- If you’re using company, campus, or hotel Wi-Fi, ports may be restricted. Try mobile data instead.
- Check that your phone’s date and time are correct. An incorrect time can cause TLS certificate validation to fail.
If the connection works after switching networks, the problem is most likely with your current network environment, not v2rayNG itself.
2. Check whether the node is working
If v2rayNG won’t connect, the next step is to check whether the node is available. Free nodes often become congested, stop working, or get temporarily blocked, so this is normal.
- On the v2rayNG home screen, long-press the node and select “Test current service connection” or a similar test option.
- If multiple nodes fail, the problem may be with your network environment or client configuration.
- If only one node fails, delete it or disable it temporarily.
- If you use a subscription, update it first, then select a node and test again.
We also compile free node resources, but their stability can vary depending on your network environment. We recommend keeping several nodes across different protocols and regions and trying them in turn.
3. Check your v2rayNG client settings
If the node appears to be working but still won’t connect, check your client settings. Beginners often overlook routing mode, VPN permissions, and conflicts with other system proxies.
- Make sure you’ve tapped the Start button in the bottom-right corner. When prompted for VPN permission, tap Allow.
- In Settings, you can leave “Enable local DNS” at its default setting. Avoid changing advanced options without a specific reason.
- For routing mode, start with “Bypass LAN and mainland addresses” or the default rules.
- If your phone has other VPNs, accelerators, or ad blockers installed, close them first to avoid conflicts.
- Try closing and reopening v2rayNG. If needed, clear the app cache and import the node again.
Make sure the node link is complete when you import it. Even a single missing character in a vmess, vless, trojan, or subscription link can prevent the connection from working.
4. Use the error message to guide your troubleshooting
Different error messages point to different possible causes. “timeout” usually means your network can’t reach the node, so try another network or node. “connection refused” may mean the node’s port is unavailable. “TLS handshake failed” is often related to the device’s time, SNI, transport settings, or an unavailable node. “context deadline exceeded” also usually indicates a connection timeout.
Don’t rush to change a bunch of settings at once. Follow the principle of changing only one variable at a time: switch networks first, then try another node, update your subscription, and reinstall the client only as a last resort. That way, you can tell which step fixed the problem.
5. Quick troubleshooting checklist
- Confirm that regular internet access works on your phone.
- Switch between Wi-Fi and mobile data and test again.
- Update your subscription or import the node again.
- Try two or three different nodes.
- Check VPN permissions, routing mode, and your phone’s time.
- If it still doesn’t work, update v2rayNG to the latest version and try again.
In summary, v2rayNG connection problems usually fall into three categories: local network restrictions, an unavailable node, or incorrect client settings. Follow the steps in this article to pinpoint the issue quickly, without deleting configurations or changing settings at random.