This article addresses the question “What should I do if v2rayNG won’t connect?” If your Android phone times out after importing nodes, fails the handshake, keeps failing speed tests, or connects but can’t open webpages, follow the checklist below to troubleshoot your phone environment, node details, client settings, and network restrictions. It’s suitable for everyday users to follow step by step.
1. Check your login and phone environment
Many connection failures aren’t caused by a bad node. Your phone’s environment may be preventing v2rayNG from handling network traffic properly. Start with these basic checks:
- Make sure your phone’s system time is set to “Automatic.” An incorrect time can cause TLS certificate verification to fail.
- Turn off other VPNs, accelerators, and proxy apps. Only one VPN tunnel can be active at a time.
- Check that v2rayNG has VPN permission. When prompted the first time you connect, tap “OK” to grant system authorization.
- Try a different network: switch from Wi-Fi to mobile data, or from mobile data to Wi-Fi.
- If you’re using a company, campus, or hotel network, access may be restricted. Try a regular home broadband connection or mobile data instead.
Once you’ve completed these steps, return to the v2rayNG home screen, tap the connect button in the lower-right corner, then open a frequently used website in your browser to test the connection. Don’t rely on the client icon alone.
2. Verify that the node and subscription are valid
If your environment checks out, look at the node itself. Free nodes can become unavailable due to congestion, expiration, or configuration changes. We also recommend regularly updating the free nodes provided on this site instead of relying on old links for too long.
- Open v2rayNG, long-press the current node, then select “Test configuration connectivity” or run a latency test.
- If multiple nodes fail, update your subscription first: open “Subscription settings” from the top-left menu, then tap the update button in the top-right corner.
- For manually imported nodes, make sure you’ve selected the correct protocol. For example, don’t confuse VMess, VLESS, Trojan, and Shadowsocks.
- Carefully check the address, port, UUID, encryption method, transport protocol, TLS, SNI, path, and other fields.
- If only one node fails, switch to another node instead of repeatedly retrying the same one.
“connection refused” usually means the port is unavailable; “timeout” often points to network blocking, an offline node, or an unreachable route; and “TLS handshake failed” means you should first check the system time, SNI, and TLS settings.
3. Check the v2rayNG client settings
Incorrect client settings can also make it seem as though you’re connected when you still can’t access the internet. Open the v2rayNG settings and, if you’re an everyday user, keep the defaults unless a change is necessary.
- For routing mode, try “Global” first. Once webpages load, you can switch to bypassing mainland China addresses.
- Enable “Local DNS” or use the client’s default DNS to avoid DNS poisoning affecting domain resolution.
- Don’t enable per-app proxying unless necessary. If you do, make sure apps such as your browser, Telegram, and YouTube are allowed to use the proxy.
- Upgrade to the latest version of v2rayNG. Older versions may not support newer configurations such as Reality, gRPC, and uTLS.
If your settings have gotten mixed up, export a backup, clear the app data, reinstall v2rayNG, then reimport your subscription or scan the node’s QR code.
4. How to pinpoint the problem if you still can’t connect
Finally, narrow down the source of the problem. First, try at least three different nodes on the same phone. Then test another network. If possible, import the same node on another Android phone. If the node works on another network, the current network is likely restricting access. If it doesn’t work on any device, the node is probably no longer active.
When troubleshooting, avoid changing a bunch of settings at once. Change just one setting at a time and note what happens. For everyday users, start with these three steps: check the system time, update the subscription, and switch networks. This checklist can quickly help pinpoint most v2rayNG connection problems.