This article addresses the question “What should I do if v2rayNG won’t connect?” Follow these troubleshooting steps in order—from checking nodes, subscriptions, time, network, and client settings to identifying risk-control triggers—to help you get a more stable connection at lower cost.
1. First, determine whether the problem is with the node or your device
If v2rayNG fails to connect, don’t immediately reinstall it over and over. In most cases, the node is unavailable, the subscription hasn’t been updated, the phone’s network is having problems, or the system time is incorrect. Try these steps to quickly narrow down the cause:
- Open v2rayNG, tap “⋮” in the top-right corner, and select “Update subscription” to make sure your node list is up to date.
- Long-press the current node and select “Test current configuration’s real connection,” or switch to another node and try again.
- Check your phone’s time: go to system settings and enable “Set time automatically” and “Set time zone automatically.” An incorrect time can cause TLS handshake failures.
- Switch networks: switch from Wi-Fi to mobile data, or vice versa, to rule out local network restrictions.
- Turn off battery-saving mode, data-management apps, and accelerator apps to prevent them from blocking v2rayNG’s background connections.
If several nodes fail to connect but the same subscription works on another phone, the problem is most likely with your device’s environment. If only one node fails, it’s usually unavailable or temporarily congested.
2. How to handle common error messages
Don’t panic if you see an error in the v2rayNG log. Tap “Log” at the bottom to get an idea of what went wrong. Here are some common errors and how to address them:
- timeout / i/o timeout: The connection timed out. Try another node or network, or try again later.
- failed to dial: The node address, port, or route is unreachable. Update the subscription and import it again.
- certificate / TLS error: Check your system time and make sure you haven’t accidentally changed the node configuration.
- Connected, but webpages won’t open: Try changing the routing mode in v2rayNG settings, such as to “Bypass LAN and mainland China addresses.”
If you’re using free nodes provided by this site, we recommend importing them by copying the subscription link rather than manually changing parameters such as the UUID, encryption, or transport protocol. Free nodes may become unstable as the number of users changes. If one stops working, update the subscription or switch nodes instead of repeatedly tinkering with the client.
3. How to avoid repeatedly triggering risk controls
In an effort to get “faster” speeds, many users switch nodes frequently, run speed tests repeatedly, and keep reconnecting. This may not improve speeds and can cause websites or network environments to flag your activity as unusual, resulting in more CAPTCHAs, login alerts, or even temporary restrictions.
A more reliable approach is to choose a working node and stick with it for a while rather than switching every few minutes. When accessing account-related websites, try to use a consistent route in the same region. Don’t run a proxy in multiple apps at the same time, and use separate connections for large downloads, video streaming, and logging in to sensitive accounts. This is generally more stable than constantly switching nodes and can also help keep costs down.
4. How to reimport a subscription correctly
- In v2rayNG, delete any nodes that are clearly unavailable or duplicated.
- Tap “+” and select “Import from clipboard” or “Subscription settings.”
- Paste the subscription link, save it, and then select “Update subscription.”
- Choose a node with low latency that passes the real connection test.
- Tap the Connect button in the bottom-right corner. Once the VPN icon appears in the status bar, open a browser to test the connection.
Finally, we recommend keeping 2–3 working backup nodes so you don’t lose access if one node has a problem. If v2rayNG won’t connect, troubleshoot in this order: “update subscription—switch nodes—check the time—switch networks—check the log.” This will usually resolve most v2rayNG connection problems.