This article addresses issues Android users may encounter with v2rayNG: “nodes appear normal but won’t connect, speed tests fail, or the connection works but websites won’t load.” We’ll troubleshoot in order of risk, checking your device settings and node first, then deciding whether to switch between Wi-Fi, mobile data, or a hotspot. This avoids immediately reinstalling the client over and over.
1. Start with basic, low-risk checks
If you’re wondering what to do when v2rayNG won’t connect, don’t rush to delete your configuration. First, make sure your phone’s time is set to sync automatically. An incorrect system time can cause TLS handshake failures. Then turn off battery saver, data saver, and background restrictions to ensure v2rayNG can keep its VPN connection running in the background.
- Open v2rayNG and make sure the correct node is selected, not an empty or outdated configuration.
- Tap the menu in the upper-right corner and use “Test current service connection” or a similar test feature.
- Go to Android settings and confirm that VPN access is allowed and isn’t being blocked by security software.
- Toggle airplane mode once, wait for the network to obtain an IP address again, then reconnect.
- If you use a subscription, update it first, then select a node and connect again.
If a free node from this site or another source stops working shortly after being imported, it may be temporarily unavailable. Try other nodes from the same subscription rather than repeatedly reconnecting to just one node.
2. Check the node and protocol settings
v2rayNG supports protocols such as VMess, VLESS, Trojan, and Shadowsocks. Common issues include missing parameters when copying a node, an incomplete subscription update, or a mismatch in SNI or transport settings. After importing a node, don’t change fields such as the address, port, UUID, encryption method, TLS, or Reality unless you know what the provider requires.
If all nodes time out, first determine whether the issue affects just one node or all of them. A single failing node is usually a node issue; if all nodes fail, the cause is more likely your device’s network, DNS, system permissions, or restrictions on the current network. In v2rayNG settings, try turning “Bypass LAN and mainland addresses” on or off, and switch system proxy modes to test. Take a screenshot of the original settings first so you can restore them if needed.
3. When to switch network environments
Switching network environments is a low-risk but effective way to narrow down the cause. There’s no need for complicated steps—just switch between Wi-Fi, mobile data, and another phone’s hotspot. We recommend testing in this order:
- If you can’t connect on your current Wi-Fi, switch to mobile data and test the same node.
- If mobile data fails, try another Wi-Fi network or ask a friend to turn on a hotspot.
- If all nodes fail on a particular network, that network may have stricter restrictions, so try switching networks first.
- If all networks fail, go back to checking the nodes, subscription, client version, and phone permissions.
Typical signs that you need to switch network environments include all speed tests timing out, the connection dropping immediately, the same node working on someone else’s phone but not on your current network, or the browser reporting that it can’t establish a secure connection. Switching networks isn’t a shot in the dark—it helps determine whether the issue lies with the node, the client, or the network connection.
4. What to do if you still can’t connect
If the issue persists after troubleshooting, update v2rayNG to a newer version and import the subscription again. Before deleting any nodes, export or save the subscription link to avoid removing it by mistake. For DNS, try turning off Private DNS on your phone or restoring the default network settings before testing again.
In short, check the time, permissions, subscription, and nodes first, then test across different network environments. Don’t keep changing protocol settings you don’t understand, and don’t repeatedly reinstall the app as a fix for every issue. Troubleshooting step by step usually helps you quickly determine whether v2rayNG is failing because a node is unavailable, the network is restricted, or the client is misconfigured.