This article addresses the common question, “What should I do if v2rayNG won’t connect?” If you import a node and see a timeout, TLS handshake failure, no internet access, or a connection that works but won’t load webpages, go through the checklist below. First rule out issues with your phone’s environment and configuration, then check whether the node itself has stopped working.
1. Check your phone’s network environment first
Many connection failures aren’t caused by v2rayNG itself, but by network conditions, system permissions, or incorrect time settings. Start with these checks:
- Make sure your phone can access the internet: Turn off v2rayNG and open a domestic website in your browser. If your local network isn’t working, switch between Wi-Fi and mobile data or restart your router.
- Check the system time: An incorrect phone clock can cause TLS certificate verification to fail. Open system settings and enable “Set time automatically” and “Set time zone automatically.”
- Turn off other proxies or VPNs: Don’t run multiple VPNs, accelerators, or packet-capture tools at the same time, as they may compete for the VPN connection.
- Check battery and background restrictions: Some Android systems restrict v2rayNG from running in the background. Allow background activity in battery settings.
- Try a different network: If Wi-Fi doesn’t work, try mobile data, and vice versa. This helps determine whether the current network is restricting the connection.
2. Check that the node and subscription are correct
If your network environment is fine, focus on the node configuration. v2rayNG supports protocols such as VMess, VLESS, Trojan, and Shadowsocks. Each protocol uses different parameters, and even a single missing character can prevent a connection.
- If you pasted a node link manually, make sure it’s complete and contains no line breaks, spaces, or Chinese punctuation.
- If you use a subscription, open the menu in the top-right corner of v2rayNG, tap “Update subscription,” then select a new node to test.
- Check whether your protocol is supported by your current version. Older versions of v2rayNG may not support some newer parameters, so consider updating to a recent version from a trusted source.
- Test several nodes instead of focusing on just one. Free nodes may be unavailable due to high usage, expiration, or routing changes.
Our site curates some free nodes and import guides for temporary testing. If all nodes fail, continue with the client settings below.
3. Troubleshoot v2rayNG client settings
In v2rayNG, long-press the current node to run a “Real connection test” or “Latency test.” If the latency looks normal but webpages won’t load, the issue is usually related to routing or DNS.
- Open “Settings” and make sure you haven’t changed “Enable local DNS” or related DNS options without a reason. If you’re unsure, restore the default settings.
- Check the routing mode: For general use, test with the default rules or global mode. If your rules are misconfigured, some websites may bypass the proxy.
- After connecting, check that the VPN icon appears at the top of your Android screen. If it doesn’t, the VPN tunnel hasn’t been established.
- Clear old configurations: Repeatedly importing subscriptions can create duplicate nodes. Delete any invalid nodes and import them again.
4. Identify the problem based on the error
Connection timed out: The node is probably unreachable, its port may be blocked, or the current network may be restricting the connection. Try another node or network.
TLS/certificate error: First check your phone’s time, the node’s domain, and whether any transport security parameters have been changed.
Connected, but webpages won’t load: Try switching the routing mode or DNS settings, or test with another browser.
Subscription update failed: Check whether the subscription link has expired or whether you need to turn off the proxy before updating. You can also paste the link into a browser to see if it opens.
5. Recommended troubleshooting order
The quickest order is: first make sure your local network is working, then correct the time and turn off other VPNs, update the subscription, test at least three different nodes, and finally adjust DNS and routing. Don’t start by changing advanced parameters at random, or it will be harder to pinpoint the problem.
If you still can’t connect after following these steps, the node is likely unavailable, the subscription may not be working, or the current network may be restricting the connection. Try a different set of nodes and keep the default settings to avoid making the client configuration more confusing.