This article addresses the issue Android users encounter when using v2rayNG: “the node has been imported but won’t connect, shows a timeout, or connects but webpages won’t open.” We troubleshoot in order of lowest risk first: first check your device settings and nodes, then determine whether you need to switch Wi-Fi, mobile data, or hotspot networks.
1. Start with low-risk basic checks
If v2rayNG won’t connect, it’s not recommended to immediately keep deleting the app or randomly changing advanced parameters. Follow the steps below first; in most cases, they can rule out the majority of configuration issues.
- Check whether your phone’s time is accurate. It is recommended to enable “Set time automatically.” Time differences may cause the TLS handshake to fail.
- Open v2rayNG, tap the menu in the top right corner, and select “Test all configurations for real connection” or test the current node.
- Make sure the current node is not from an expired subscription. If the node comes from this site’s free node page, you can copy the subscription link again and update it once.
- Check the system VPN permission: when connecting, a VPN request should pop up, and you need to tap Allow. If you previously denied it, go to system settings, clear v2rayNG’s VPN configuration, and try again.
- Switch to other nodes in the same subscription to avoid mistaking a single node failure for a software issue.
If the test results show timeout, context deadline exceeded, or connection refused, it usually means the connection path is blocked, the node is unavailable, or the current network has heavy restrictions.
2. Check proxy mode and routing settings
If v2rayNG can connect but webpages won’t open, a common reason is that the proxy mode is not set correctly. For ordinary users, it is recommended to first test with Bypass LAN and mainland China addresses or Global mode. If Global works but routing mode does not, the rules or DNS may be the problem.
You can go into settings and temporarily disable complex routing, ad blocking, or custom DNS, then reconnect using the default configuration. It is also recommended to test with a different browser, such as Chrome and the system browser, to avoid interference from browser cache or extensions.
3. When you need to change the network environment
If the node works on someone else’s phone, or if multiple nodes all fail when you switch between them, you should consider the current network environment. In the following situations, it is recommended to change networks:
- Office, school, or hotel Wi-Fi: these networks often have gateway inspection, port restrictions, or DNS hijacking, which can easily cause connection timeouts.
- If all nodes suddenly become unavailable on your home broadband: first restart the modem and router, then try mobile data on your phone.
- If mobile data works but Wi-Fi does not: the problem is most likely with the router, broadband DNS, or LAN restrictions.
- If Wi-Fi works but mobile data does not: this may be due to differences in the carrier’s mobile network policies. It is recommended to toggle airplane mode or switch between 4G and 5G.
A low-risk way to change networks is: first switch from Wi-Fi to mobile data; if that doesn’t work, toggle airplane mode; if it still doesn’t work, ask another phone to enable a hotspot for testing. This will not damage your existing configuration.
4. What to do if it still won’t connect
As you continue troubleshooting, it is recommended to keep one “known working” node as a reference. First update v2rayNG to the latest version, then re-import the subscription. Do not manually change fields such as UUID, address, port, or transport protocol. Many connection failures are caused by incomplete copying or subscription cache issues.
Finally, you can check the v2rayNG logs. If terms such as TLS, handshake, EOF, or timeout appear repeatedly, give priority to changing the node or network. If it indicates configuration parsing failed, then re-import the subscription. Remember this troubleshooting order: first the node, then the software, then the network. Do not repeatedly make random changes to advanced settings. Free nodes can be used as a temporary testing source, but their stability will be affected by the route and the number of users, so it is recommended to prepare multiple backup nodes.