This article addresses the problems Android users may encounter with v2rayNG, such as suddenly being unable to connect, failed speed tests, timeouts, or being connected but unable to open webpages. It also explains how to determine, using low-risk checks, whether the issue is with a node, the client configuration, or the current network environment.
1. Start with these low-risk checks
If you’re wondering what to do when v2rayNG won’t connect, don’t start by deleting the app or changing settings at random. Follow the checks below in order; they’re unlikely to affect your existing configuration.
- Check that your phone’s network is working: Stop v2rayNG and open a domestic website in your browser to confirm that your Wi-Fi or mobile data can access the internet.
- Test another node: If you’ve imported a subscription, tap the update button in the top-right corner, then try connecting to another VLESS, VMess, or Trojan node.
- Check your system time: A significant time discrepancy can cause TLS handshake failures, so it’s best to enable “Set time automatically.”
- Toggle the VPN connection: Stop the service in v2rayNG, then reconnect. If needed, close the app in the background and reopen it.
- Check the routing mode: Most users should start with the default rules. Avoid enabling advanced options such as global mode or bypassing the LAN unless necessary.
If you’re using free nodes provided on this site, we recommend importing them by copying the full subscription link to avoid missing fields such as the port, UUID, or transport protocol when entering details manually.
2. How to tell whether a node is unavailable
An unavailable node is the most common cause. Symptoms include failed latency tests, disconnections immediately after connecting, or log messages such as timeout, connection refused, and TLS handshake failed. Here’s how to check:
- If only one of several nodes fails on the same network, that node is probably unavailable.
- If the same node continues to fail at different times while other nodes work, consider deleting it or avoiding it for now.
- If you haven’t updated your subscription in a while, the node addresses may have changed. Update the subscription before testing again.
Keep in mind that free nodes may not always be available, so a single failed connection doesn’t necessarily mean the client is broken. A more reliable approach is to prepare 2–3 nodes from different sources and test them one by one.
3. When to try a different network
If none of your nodes can connect, consider whether the current network is imposing restrictions. Trying a different network doesn’t involve any risky changes; it’s simply a way to cross-check the connection.
- Switch from Wi-Fi to mobile data and try connecting to the same node.
- Switch back from mobile data to Wi-Fi, or test on a different router’s network.
- If the connection fails on a company, school, or hotel network, try again on your home network or mobile data.
If the same nodes work on mobile data but all fail on a particular Wi-Fi network, that Wi-Fi network is probably not suitable for proxy connections. Conversely, if they fail on every network, the issue is more likely related to the subscription, nodes, or client configuration.
4. If it still fails, check the logs and back up before reinstalling
You can view the logs from the menu in the top-right corner of v2rayNG. Most users only need to look for a few keywords: timeout usually indicates a network timeout; DNS-related messages may point to a name resolution issue; and certificate or TLS messages are often related to the node configuration, system time, or certificates.
Only consider clearing the app data or reinstalling as a last resort. Before doing so, export your configuration or save your subscription link to avoid losing your nodes. Remember this troubleshooting order: first test your phone’s network, then try another node, update the subscription, and only then switch networks or reinstall. This approach takes the least effort and helps prevent making the problem worse by changing too many things.