This article addresses the common issue of “what to do if v2rayNG won’t connect” and focuses on low-risk steps: first check your phone, nodes, subscription, and network environment, without changing underlying system settings or involving a self-built server. It is suitable for ordinary users to quickly troubleshoot step by step.
1. First, confirm whether it is a basic settings issue
Many connection failures are not caused by expired nodes, but by incorrect import settings, time, permissions, or proxy mode configuration. It is recommended to check in the following order first, to avoid frequently switching configurations right away.
- Open v2rayNG and confirm that the correct node is selected. There is usually a selection mark on the left side of the node.
- Tap the latency test in the upper right corner or “Test all configurations.” If they all time out, do not rush to delete them.
- Check whether your phone’s time is set to sync automatically. If the time difference is too large, it may cause the TLS handshake to fail.
- Make sure v2rayNG has been granted VPN permission. At first launch, you need to allow the system to create a VPN connection.
- Go into settings and check the routing mode. For ordinary users, it is recommended to first use “Bypass LAN and mainland China addresses” or the default configuration.
If you are using the free nodes compiled by this site, it is also recommended to copy the subscription address again or update the subscription to avoid incomplete configurations caused by old cache.
2. The correct order for updating subscriptions and switching nodes
When a single node fails to connect, it is not recommended to repeatedly turn the app on and off too many times. A more reliable approach is to update the subscription first, then switch nodes one by one for testing.
- Click “Update subscription” in the subscription group, wait for it to finish, and then test again.
- Give priority to nodes with lower latency and normal test results.
- If a node shows a timeout, you can first switch to other nodes in the same region or using the same protocol.
- Do not import too many configurations from unknown sources at the same time, to avoid duplicate routing and abnormal rules affecting your judgment.
If only one node fails, that node is usually temporarily unavailable; if all nodes fail, the problem is more likely to be with the local network, DNS, system permissions, or subscription format.
3. When you need to change the network environment
Changing the network environment is a very effective low-risk troubleshooting step, but it should not be the first step. In the following situations, you can try switching from Wi-Fi to mobile data, or changing to another Wi-Fi network and testing again:
- All nodes show timeout, connection refused, or TLS handshake timeout.
- The same subscription works on someone else’s phone, but not on your current network.
- It does not connect on public Wi-Fi or a company/campus network, but mobile data on your phone may work normally.
- Web pages can open, but v2rayNG keeps showing as connected while still being unable to access the external network.
Changing the network environment is intended to determine whether the current network is restricting proxy connections. For example, some public networks may restrict UDP, proxy ports, or long connections. In this case, the app itself is not broken.
4. Safe handling when it still won’t connect
If the above steps do not work, you can try clearing the app cache, restarting the phone, and re-importing the subscription. Be careful not to casually install an untrusted “fixed version” client, and do not send your subscription link to strangers for troubleshooting, because the subscription may contain information about your available nodes.
Finally, it is recommended to keep one working node as a reference: if the new node fails while the old node works normally, it is most likely a problem with the new configuration; if all of them fail, then consider the network environment or client version. When troubleshooting, follow the principle of “simple first, complex later,” and you can usually identify the reason why v2rayNG won’t connect.