This article addresses the common question, “What should I do if v2rayNG won’t connect?” It walks you through troubleshooting nodes, subscriptions, network connectivity, and client settings, and explains how to reduce the risk of rate limits or other restrictions caused by frequent switching and repeated reconnections—so you can use free nodes more reliably and with less hassle.
1. First, check whether the node itself is down
If v2rayNG reports a connection failure, timeout, or TLS handshake failure, the problem often isn’t your phone. The node may have expired, been blocked, run out of quota, or become temporarily unavailable. Start with these three steps:
- Open v2rayNG, long-press the current node, and select “Test current configuration connection” or “Test all configurations connection.”
- If only one node fails, test other nodes from the same subscription. If they all fail, check your subscription and network next.
- Make sure your system clock is accurate. A significant time difference can cause TLS certificate validation errors.
This site curates free node resources, but free nodes are shared by many users, so their reliability can fluctuate. Don’t rely on a single node; keep 2–3 working backups available.
2. Check that your subscription has updated successfully
If you imported nodes using a subscription link, the link may have expired or the subscription may not have refreshed. To check, open the menu in the upper-left corner of v2rayNG and select “Subscription settings.” Make sure there are no extra spaces in the link, then return to the main screen and tap “Update subscription” in the upper-right corner. Once the update is complete, test the latency and connection.
Keep in mind that refreshing your subscription frequently or running many speed tests in a short time may look like unusual activity to the server and result in a temporary restriction. A more reliable approach is to update your subscription once or twice a day at set times rather than refreshing it every few minutes. When testing speeds, stick to the regions you use most; there’s no need to test every node repeatedly.
3. Check your phone’s network and proxy settings
Wi-Fi, mobile data, DNS, or battery-saving settings can also affect your connection. Try these steps in order:
- Switch between Wi-Fi and mobile data to see whether one network is blocking the connection.
- Turn off system battery saver and allow v2rayNG to run in the background.
- In v2rayNG settings, check that “Enable local DNS” and your routing settings haven’t been changed accidentally.
- If the connection works but webpages won’t load, check whether your browser has another proxy extension enabled.
On Android, some security apps may kill background VPN processes, causing the connection to drop soon after it starts. Add v2rayNG to the app’s allowlist and keep the VPN icon visible in the notification bar.
4. Reduce the risk of triggering restrictions: switch less, avoid concurrent connections, and choose stable nodes
To find a fast node, many users switch through a dozen nodes and repeatedly turn the connection on and off. This may not make the connection any faster and can cause node providers to flag the activity as unusual. To balance cost and reliability, choose a node that reliably opens the websites you use most rather than focusing only on the lowest latency.
For everyday use, connect to the same node on only one device at a time. Don’t run downloads and speed tests while also logging in on multiple devices. When watching videos, choose a reasonably stable node and avoid switching frequently. If a node fails several times in a row, stop using it for a while and switch to a backup.
5. Final checks if you still can’t connect
If none of the above works, try updating v2rayNG to a newer version, deleting the old configuration, and importing the subscription again. Also make sure the client supports the node’s protocol and that all required fields are present, such as those for VLESS, VMess, Trojan, or Reality. A “configuration format error” usually means the link wasn’t copied completely or the QR code wasn’t scanned correctly.
In short, if v2rayNG won’t connect, don’t keep reconnecting blindly. Troubleshoot in this order: check whether the node is available, confirm the subscription is up to date, check your network, and verify the client settings. Limiting how often you refresh and switch nodes will usually improve connection stability without adding much cost.