This article addresses the common question, “What should I do if v2rayNG won’t connect?” It skips the complicated technical details and walks you through checks in four areas: your network environment, node configuration, network permissions, and subscription updates. It’s designed for Android users to follow as they troubleshoot.
1. First, check that your network environment is working properly
Many connection failures aren’t caused by a problem with v2rayNG itself, but by an unstable network on your phone. Start with these basic checks:
- Switch networks: Switch between Wi-Fi and mobile data to rule out network restrictions or DNS issues.
- Disable battery restrictions: In your phone’s settings, allow v2rayNG to run in the background so the system doesn’t kill it just after it connects.
- Check your time: Turn on “Set time and time zone automatically.” An incorrect time can cause TLS certificate verification to fail.
- Check for proxy conflicts: If you’re also using another VPN, accelerator, or ad-blocking app, close them all and leave only v2rayNG running.
Once you’ve done this, reopen v2rayNG and tap “Test connection for all configurations” in the top-right menu, or connect to a node directly to test it.
2. Check that your nodes and subscription are working
If your network environment is fine, check your nodes next. Free nodes often stop working because they expire, become congested, are blocked, or have their configurations changed. This site also provides information on some free nodes, but we recommend making a habit of updating your subscription regularly.
- Manual nodes: Carefully check the address, port, UUID, transport protocol, TLS, SNI, path, and other fields. Even a single incorrect character can prevent a connection.
- Subscription nodes: Pull down to refresh on the v2rayNG home screen, or open subscription settings and tap “Update subscription.”
- Test multiple nodes: Don’t test just one. Try 3–5 nodes in a row to see whether the problem is limited to a single node.
- Check error messages: A timeout usually indicates a network issue or an unreachable node; a handshake failed error is often related to TLS, the device’s time, or SNI.
If all nodes fail but the same subscription works on another device, the issue is probably with the phone’s local environment. If the subscription also fails on other devices, the subscription or nodes may no longer be working.
3. Check the v2rayNG client settings
After opening v2rayNG, check the following settings. First, make sure the icon in the bottom-right shows that you’re connected and that the VPN indicator appears in the status bar. Next, for routing mode, most users should select “Bypass LAN and mainland China addresses.” Avoid enabling rules you’re unfamiliar with. Finally, open “Settings” and check that your local DNS settings aren’t filled in incorrectly. If you’re not sure, restore the defaults first.
If you imported a VLESS, VMess, Trojan, or other node, check your client version. Older versions of v2rayNG may not support some newer parameters, so we recommend updating to a recent version from a trusted source. If the problem persists after updating, delete the node and scan its QR code again or reimport it from the clipboard to rule out issues with old cached data.
4. Quick troubleshooting steps if you still can’t connect
- Restart your phone, then open v2rayNG and try connecting again.
- Update your subscription and try a node in a different region or using a different protocol.
- Close any other VPN, proxy, or security apps.
- Check your system time and switch between Wi-Fi and mobile data.
- Update v2rayNG, delete the old configuration, and import it again.
In short, v2rayNG connection failures usually have more than one possible cause. Troubleshoot in this order: network environment → node availability → client settings → system permissions. Avoid changing complicated settings repeatedly. First, use a working subscription or a free node listed on this site to confirm that the client can connect, then determine where the problem lies.