This article addresses the question, “What should I do if v2rayNG won’t connect?” It walks you through troubleshooting your phone’s network, system permissions, node validity, subscription updates, and common error messages. It’s intended for Android users who have already imported V2Ray/VLESS/VMess nodes but still can’t connect.
1. Check your phone’s network environment first
Many connection failures aren’t caused by a faulty client. They’re often due to network conditions or system permissions. Start with the checklist below instead of repeatedly reinstalling the app.
- Switch networks: Switch from Wi-Fi to mobile data, or vice versa. Some workplace, campus, and hotel Wi-Fi networks restrict proxy connections.
- Disable other VPNs: Android usually allows only one VPN service to run at a time. First, quit any accelerators, packet capture tools, or VPN-based ad blockers.
- Check your system time: A significant time discrepancy can cause TLS handshake failures. We recommend enabling “Set time automatically.”
- Allow background activity: Some phones may suspend v2rayNG. Go to your battery settings and allow it to run in the background.
- Confirm that your local network is working: Open a domestic website in your browser first to rule out a lost connection, unpaid bill, or router issue.
2. Check whether your nodes and subscription are valid
If your network environment is fine, check your nodes next. Free nodes often become unavailable, congested, or blocked. This site also curates free nodes, but you should test them on your own device to confirm they work.
- Open v2rayNG, go to the node list, and long-press the current node. Select “Test real connection” or “Test latency.”
- If the latency test fails, try another node instead of repeatedly reconnecting to the same one.
- If you use a subscription, tap the menu in the top-right corner and select “Update subscription,” then test again.
- Make sure the node protocol is compatible with the client. For example, avoid accidentally changing VLESS, VMess, or Trojan settings.
- Delete any clearly duplicated or expired nodes so you don’t select an outdated configuration by mistake.
Note: Low latency doesn’t guarantee that you’ll be able to access sites outside your country. Use the real connection test and actual browsing results as your guide.
3. Check the basic v2rayNG settings
Go to the v2rayNG settings page. Most users only need to check the following. For routing, start with “Bypass LAN and mainland addresses” so domestic websites connect directly while overseas websites use the proxy. If DNS is being tampered with, try enabling built-in DNS or switching to a commonly used public DNS. If you’re unsure what an advanced option does, restore the default settings. Avoid enabling features such as sniffing, per-app proxy, or Mux without a clear reason.
To connect, tap the circular button at the bottom. When Android displays the VPN authorization prompt, tap Allow. If there’s no key icon in the status bar, the VPN tunnel may not have been established successfully.
4. How to identify common errors
- context deadline exceeded: Usually means the node is unreachable, the network is blocking the connection, or the server isn’t responding. Try another node or network first.
- connection refused: The destination port is refusing the connection. The node may be unavailable or configured with the wrong port.
- tls handshake failed: This may be caused by an incorrect system time, an invalid SNI or domain, or mismatched TLS settings.
- failed to read response: Often caused by network instability, a congested node, or incorrect protocol parameters.
We recommend troubleshooting in this order: switch networks, update your subscription, try another node, and then check the client settings. Don’t change too many options at once, or it’ll be difficult to tell what fixed the problem—or caused it.
5. What to do if you still can’t connect
If all nodes fail, uninstall v2rayNG, install the latest version, and import your subscription again. You can also copy the same node into another client, such as Clash or sing-box, and test it there. If it works in another client, the problem is probably with your v2rayNG settings. If it fails in every client, the node or your current network environment is the more likely cause. Working through the checklist step by step will usually help you identify most v2rayNG connection problems.