This article addresses what ordinary users should check first in their sign-in environment and client settings when v2rayNG on a phone cannot connect after importing a node, shows a timeout or TLS handshake error, or connects but cannot open webpages. Follow this practical checklist to troubleshoot the issue; server-side configuration is not covered.
1. Check your basic connection environment
Many “what should I do if v2rayNG won’t connect?” issues aren’t caused by a faulty node, but by basic conditions such as the phone’s network, system time, or proxy settings. Check these in order:
- Check your phone’s network: Turn off v2rayNG and use a browser to visit a domestic website, confirming that Wi-Fi or mobile data is working. If your workplace or campus Wi-Fi is restricted, switch to mobile data and test again.
- Set the correct system time: Go to your phone’s settings and enable “Set date and time automatically.” A significant time discrepancy can cause TLS certificate verification to fail.
- Turn off other proxies/VPNs: Don’t run multiple VPNs, accelerators, or packet-capture tools at the same time, as this can cause routing conflicts.
- Check that battery-saving restrictions are off: Some Android systems restrict background VPN activity. Allow v2rayNG to run in the background and launch automatically.
If you’re using a free node provided by this site, copy the latest subscription or node link first to avoid using outdated information.
2. Check that the node and subscription were imported correctly
Open v2rayNG and long-press the current node to check that the address, port, UUID, transport protocol, security type, and other details haven’t been truncated. To import via subscription, tap the menu in the top-right corner and select “Update subscription.” If the update fails, try opening the subscription link in a browser to see if it’s accessible. If it won’t open, the subscription URL, network, or name resolution may be the problem.
- The node has expired or been removed: Try another node from the same subscription.
- Extra spaces were copied: Copy the complete vmess, vless, trojan, or subscription link again.
- Protocol mismatch: Don’t mix parameters for VLESS, VMess, Trojan, and Shadowsocks.
- Missing SNI/Host: Some nodes rely on domain name obfuscation, and an incomplete import can cause connection failures.
3. Use logs to identify common errors
v2rayNG’s logs are useful. Open “View logs” in the menu, or tap the logs after a connection failure, and focus on the last few lines.
If you see timeout or i/o timeout, the network usually can’t reach the node. Switch networks or try another node. If you see certificate or TLS handshake errors, first check the system time, TLS settings, and SNI. If you see authentication failed, the UUID, password, or protocol parameters are probably incorrect. If you see no route or network unreachable, there may be an issue with the local network, DNS, or system VPN permissions.
4. Recommended quick fixes
- Restart v2rayNG and tap Allow in the system VPN permission prompt.
- Update the subscription, select a new node, and tap the connect button in the bottom-right corner.
- In “Routing settings,” start with the default rules instead of configuring complex routing right away.
- Change DNS settings: Try the app’s default DNS, or turn off Private DNS and test again.
- If it still fails, switch between Wi-Fi and mobile data, then check the relevant keywords in the logs.
How to tell: Once connected, a VPN icon should appear in the status bar. Then use a browser to test a website that requires a proxy. If the icon appears but webpages won’t open, check routing, DNS, and whether the current node is available. Working through this checklist should usually help you determine whether v2rayNG can’t connect because of the environment, an import issue, or an unavailable node.