This article addresses the common question, “What should I do if v2rayNG won’t connect?” If you can’t get online after importing nodes, see timeouts or handshake errors, or tests keep failing, work through the checklist below. First check your phone’s network, time, node details, and proxy settings, then decide whether you need to switch nodes.
1. Check your phone’s network environment
Many connection failures aren’t caused by a problem with v2rayNG itself, but by an unstable network. Start with these basic checks:
- Switch networks: Test both Wi-Fi and mobile data to rule out restrictions on your current network.
- Turn off battery saver: Some phones’ power-saving settings can restrict background VPN connections.
- Check the system time: A significant time discrepancy can cause TLS handshake failures, so enable automatic time settings.
- Close other VPN apps: Don’t run multiple proxy or accelerator apps at the same time.
- Check app permissions: Allow v2rayNG to use VPN, run in the background, and access the network.
If it works immediately after you switch networks, the issue is probably with the original network, such as a school, work, or public Wi-Fi network that restricts proxy connections.
2. Check that your nodes and subscription are working
Open v2rayNG, long-press the current node, and select a connectivity or latency test. If every node times out, don’t keep tapping Connect. Instead, try these steps in order:
- Update your subscription: Tap the menu in the upper-right corner, select “Update subscription,” and wait for the node list to refresh.
- Switch nodes: Test nodes in different regions or on different routes rather than repeatedly trying the same one.
- Check the link format: If you imported a link manually, make sure the vmess, vless, trojan, or other link was copied in full.
- Import the node again: Delete any problematic nodes, then copy and import them again from the subscription URL or our free nodes page.
Keep in mind that free nodes can be affected by the number of users and the condition of the route, so temporary outages are normal. Keep several working nodes available so you can switch if one stops connecting.
3. Check your v2rayNG settings
If a node appears to be working but you still can’t open webpages after connecting, check the client settings. In v2rayNG’s settings, make sure “Routing mode” hasn’t been set to proxy only for the local network. Most users should start with the default routing mode or the mode that bypasses LAN and mainland China addresses. Incorrect DNS settings can also let you connect while preventing websites from opening, so try restoring the defaults.
Some nodes also require support from a newer core. Update to the latest version of v2rayNG from a trusted app store or the project’s release page. Before updating, take a screenshot of your subscription URL so you can find the source of your nodes if you need to set things up again.
4. How to interpret common errors
- timeout: Often caused by an unavailable node, network blocking, or an unresponsive server. Try switching nodes and networks first.
- TLS handshake failed: Check your phone’s time and make sure the node’s transport security settings match.
- connection refused: The node’s port may be closed or the route may no longer work. Try updating your subscription.
- Connected, but webpages won’t open: Check DNS, routing mode, and whether your browser is using the proxy.
We recommend troubleshooting in this order: switch networks, check the time, update your subscription, switch nodes, restore the default settings, and update the client. This makes it easier to pinpoint the problem without resorting to an unnecessary reinstall. If multiple nodes fail on different networks, your subscription source may no longer be working; get a new set of working nodes.