This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow these steps to troubleshoot your nodes, subscription, mobile network, time settings, and potential security restrictions—in order—to restore your connection with minimal effort and avoid the instability that can come from switching nodes too often.
1. First, check whether the node itself is unavailable
Many connection failures aren’t caused by a problem with the client. The node may have expired, been blocked, have an unavailable port, or require a subscription update. Open v2rayNG, go to the node list, and long-press the current node. Select “Test current service connection” or use the test function in the top-right corner. If the latency test keeps failing, try another node from the same subscription.
- Open v2rayNG and go to the node list.
- Tap the menu in the top-right corner and select “Update subscription.”
- After updating, don’t test every node at once. Start by testing 2–3 frequently used regions.
- Select a node with a normal latency result, then tap the button in the bottom-right corner to reconnect.
If you’re using free nodes curated by this site, we also recommend reimporting them or updating the subscription regularly. Free node availability can change, so they aren’t guaranteed to stay online.
2. Check your phone’s basic settings
v2rayNG can be sensitive to your system time and network environment. First, make sure your phone is set to “Set time automatically” and that the time zone is correct. Then try switching networks—for example, switch from Wi-Fi to mobile data, or restart your router. If you can’t connect only on a particular Wi-Fi network, that network may be restricting proxy traffic.
Also check whether Android is preventing the app from running in the background. In system settings, find v2rayNG, allow background activity, and turn off battery optimization. Make sure another VPN or acceleration app isn’t using the local VPN permission. Only one VPN app can be active at a time.
3. Check the protocol and import format
If you’ve manually imported a VLESS, VMess, Trojan, or other node, common mistakes include extra spaces in the address, an incorrect port, an incomplete UUID, or missing TLS or Reality parameters. If you’re not an experienced user, avoid entering the details one by one. Importing from a copied link or subscription is less likely to result in formatting errors.
- VMess links usually start with vmess://.
- VLESS links usually start with vless://.
- A subscription address is usually an https link; don’t import it as an individual node link.
- A correctly displayed name after import doesn’t guarantee the node will connect. You still need to test the connection.
4. How to avoid triggering security restrictions
For better stability and lower overhead, avoid frequently refreshing your subscription, running large-scale latency tests back to back, or switching regions repeatedly in a short period. These actions may cause nodes to be rate-limited or temporarily unavailable. We recommend sticking to a small number of stable nodes instead of testing every node whenever you open the app.
A more reliable setup is to keep one primary node, one backup, and one emergency node in a different region. For light activities such as browsing and research, try to use the same node consistently. If the connection suddenly drops, wait a few seconds before reconnecting instead of rapidly tapping the connect button. This helps reduce unusual requests and lowers the chance of free nodes being temporarily restricted.
5. Quick fixes if you still can’t connect
Try these steps in order: update the subscription, switch networks, restart v2rayNG, restart your phone, and delete and reimport the subscription. If all nodes fail, the subscription source may be unavailable or your current network may be interfering with the connection. Don’t keep changing advanced settings; first try a different set of working nodes to check whether the client is functioning normally.
In summary, if v2rayNG won’t connect, first check node availability, your system time, network environment, and import format. Avoid frequent testing and switching while using the app. These steps can usually improve stability without adding any cost.