This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow this checklist to check your phone’s network, system permissions, node details, subscription updates, and routing mode. It can help you quickly determine whether the issue is your environment, an inactive node, or an incorrect client configuration.
1. Check your phone’s network environment first
Many connection failures aren’t caused by v2rayNG itself, but by network conditions or system restrictions. Work through these checks in order:
- Switch networks: switch from Wi-Fi to mobile data, or vice versa, to rule out network blocking, DNS issues, or router restrictions.
- Turn off other VPNs: Android usually allows only one VPN connection at a time. If Clash, a network accelerator, or security software is also running, exit it first.
- Check the date and time: If your phone’s clock is significantly off, the TLS handshake may fail. Turn on “Set time automatically.”
- Confirm permissions: The system will prompt you to authorize the VPN the first time you connect. You must tap “OK” to establish the tunnel.
- Disable battery restrictions: Some phones freeze v2rayNG in the background. Go to the app’s battery settings and allow it to run in the background.
2. Check that your nodes and subscription are working
If your environment checks out, check your nodes next. Free nodes may be inactive, congested, or unreachable from your region, so don’t test just one.
- Open v2rayNG, long-press the current node, and select “Test current configuration (real connection)” or “Test all configurations (real connection).”
- If the test times out or fails, try another VLESS, VMess, or Trojan node.
- If you use a subscription, tap the menu in the top-right corner and select Update subscription to avoid using an outdated configuration.
- When importing free nodes from this site, copy the entire link. Don’t omit the prefix, such as vmess:// or vless://.
Note that a successful latency test doesn’t necessarily mean you can access every website. A real connection test is a better indicator of whether a node will work in practice. If all nodes fail, suspect your network environment or an expired subscription first.
3. Check your v2rayNG settings
In the v2rayNG settings, most users only need to check a few items. First, make sure the core version isn’t too old. If the version from your app store seems outdated or problematic, consider updating to the latest version. Next, check “Routing settings.” Beginners should stick with the default mode or the option to bypass LAN and mainland China addresses. Avoid enabling complex rules without a good reason.
If you imported a node manually, make sure the address, port, UUID, encryption method, transport protocol, TLS, SNI, and other fields are correct. Configurations such as VLESS Reality, WebSocket, and gRPC are especially sensitive to missing or incorrect parameters—even one missing field can prevent a connection.
4. Use the logs to identify the cause
Tap the menu in the top-left corner of v2rayNG and open the logs to see the likely reason for the failure. Common messages include:
- timeout: Usually means the node is unreachable, the network is blocking the connection, or the port is blocked.
- connection refused: The server port may be closed, or the node may no longer be active.
- tls handshake failed: TLS, SNI, certificate, or time settings may be incorrect.
- no route or dns error: Routing rules, DNS, or name resolution on the current network may be at fault.
When troubleshooting, change only one thing at a time: switch networks first, then try another node, update your subscription, and finally check the client settings. Changing several options at once makes it much harder to identify the cause.
5. Quick fixes
If you don’t want to troubleshoot each item in detail, try these steps in order: restart your phone and v2rayNG; switch between Wi-Fi and mobile data; update your subscription; test all nodes; update the client; delete any problematic nodes and import them again. Most connection issues can be diagnosed with these steps. If the problem persists, note the relevant log messages, node protocol, and current network environment, then continue checking the items above.