This guide explains what to do when v2rayNG won’t connect. Without changing your phone’s system settings or deleting configurations indiscriminately, check your nodes, subscription, network, and client settings in order of risk, and learn when to switch between Wi-Fi, mobile data, or another node.
1. First, check whether the issue is with the node or subscription
Many connection failures aren’t caused by a problem with your phone. The node may be down, the subscription may need updating, or an incorrect system time may cause the handshake to fail. Start with the easiest fixes.
- Open v2rayNG, long-press the current node, and select “Test real connection” or “Test all configurations.” If only one node fails, try another node from the same subscription first.
- Go to your subscription settings and tap Update subscription. Free nodes provided by this site may also become unavailable due to network fluctuations, so update the subscription before testing again.
- Check that your phone’s time is set to update automatically. A significant time difference can cause TLS certificate verification to fail.
- Make sure the configuration hasn’t been changed by mistake. An incorrect address, port, UUID, transport protocol, TLS setting, or SNI can prevent a connection.
If multiple nodes time out after you update the subscription, continue by checking your local network.
2. Low-risk checks for your phone and v2rayNG settings
Don’t uninstall the app or clear all its data just yet. Check each item below in turn. These steps often fix issues such as “connected but pages won’t load” or “test failed.”
- Turn the switch in the bottom-right corner of v2rayNG off and back on, then wait 5–10 seconds before testing a webpage.
- Make sure you’ve granted the system VPN permission. A VPN icon should appear in the status bar.
- Check “Routing mode” in v2rayNG settings. Most users can start with “Bypass LAN and Mainland China addresses” or the default mode.
- Temporarily turn off battery saver, data management, and third-party security apps to prevent v2rayNG from being stopped in the background.
- If pages won’t open in just one browser, try Chrome or Edge, or clear the browser’s proxy settings.
Note: Don’t enable advanced features you don’t understand, such as custom DNS, MUX, or fragmentation. These may help in some cases, but they can also make troubleshooting more complicated.
3. When to try a different network
If multiple nodes won’t connect and you’ve confirmed that the configuration is correct, your current network may be restricting the connection. Trying a different network means switching between Wi-Fi, mobile data, or a hotspot. It doesn’t involve higher-risk steps like flashing your phone or changing router settings.
Try this sequence: switch from Wi-Fi to mobile data first. If mobile data works, your Wi-Fi network may be restricting proxy connections. Then try another Wi-Fi network, such as your home or office network, or a phone hotspot. If Wi-Fi works but mobile data doesn’t, your carrier’s network may not support the port or protocol well.
On public Wi-Fi, first open a regular webpage to check whether there’s a login page. v2rayNG will often time out if you haven’t signed in. Complete the login first, then start the proxy.
4. What to do if you still can’t connect
If none of the steps above work, try a minimal reset: update v2rayNG to a recent version, re-import the subscription link, and test a node using a different protocol or region. Avoid importing too many duplicate configurations, which can make it easy to select an outdated node by mistake.
When troubleshooting, remember this rule: try another node first, then another network, and reinstall the client only as a last resort. This is the lowest-risk approach and makes it easier to pinpoint the problem. If the error message includes “timeout,” “TLS handshake failed,” or “connection refused,” save a screenshot and continue troubleshooting based on the specific message.
In summary, when v2rayNG won’t connect, check the subscription and nodes first, then check VPN permissions, routing mode, and battery restrictions. If multiple nodes fail on the same network, try switching to a different network. Following this order can help you avoid accidentally deleting configurations or wasting time on ineffective fixes.