This article addresses a common problem: when v2rayNG on your phone suddenly stops connecting, nodes time out, or you can connect but websites won’t load, how can you troubleshoot safely and decide when to switch between Wi-Fi, mobile data, or a different subscription?
1. First, check for basic configuration issues
Many v2rayNG connection failures aren’t caused by a faulty app. They may be due to an expired subscription, an unavailable node, or another app using the system’s network connection. Check the following in order, and avoid repeatedly uninstalling the app as a first step.
- Open v2rayNG and make sure the selected node isn’t an empty configuration. Check that its address, port, UUID, and other details haven’t been accidentally deleted.
- Tap the menu in the upper-right corner, select Update subscription, and wait for the update to finish. Then select another node and try connecting again.
- Check that your phone’s time is correct. We recommend enabling “Set time automatically,” as an incorrect time can cause TLS handshake failures.
- Close any other VPN, accelerator, or proxy apps. Use only one VPN connection at a time—v2rayNG.
- Test with another browser, such as Chrome, and open a familiar website. This helps rule out a problem with a specific app rather than the node.
If you’re using the free nodes provided on this site, update your subscription before testing. Free node availability can fluctuate depending on network conditions.
2. Use the logs to identify common errors
You don’t need to understand every v2rayNG log entry, but a few keywords can be useful. Open “Logs” from the sidebar or menu, connect once, then check the last few lines.
timeoutori/o timeout: The node may be unreachable, the network may be blocking the connection, or the current network quality may be poor.TLS handshake failed: The time may be incorrect, the SNI may not match, or the node configuration may be invalid.connection refused: The server port may be unavailable, or the node may no longer work.- No change in the logs: Your device may be blocking VPN access, restricting the app to save power, or the app may not have started properly.
For timeout errors, first try another node in the same subscription. Avoid repeatedly changing transport settings you don’t understand, as this could break a configuration that was working.
3. When should you switch network environments?
Switching network environments means changing from home Wi-Fi to mobile data, or from your current carrier’s network to another Wi-Fi network. This is a low-risk step that won’t change your node configuration, and it can help you determine whether the problem is with the node or your local network.
Try switching networks if:
- The same node times out on Wi-Fi but connects on mobile data.
- All nodes fail on your current Wi-Fi, but work for other people or on other networks.
- The logs repeatedly show
timeout, and regular web browsing is also noticeably slow. - You can’t connect on a public network at work, school, or a hotel, but everything works normally on your home network.
It’s simple: disconnect v2rayNG, turn off Wi-Fi, enable mobile data, and reconnect to the node—or switch back from mobile data to Wi-Fi. For testing, use just one node to avoid introducing too many variables.
4. What if you still can’t connect?
If the connection still fails after switching networks, try these other low-risk steps: clear v2rayNG from the background and restart the app; remove the old VPN authorization in your system’s VPN settings and approve it again; update v2rayNG to a newer version; or delete the invalid subscription and import the subscription link or node QR code again.
As a final check, try these three steps: switch nodes, switch networks, and update the client. If switching nodes works, the original node is no longer available. If switching networks works, the current network is likely restricting the connection. If updating the app works, the issue was likely a client compatibility problem. Following these steps in order should help you avoid making unnecessary changes to your configuration.