This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on low-risk troubleshooting that doesn’t involve changing system settings or adjusting advanced parameters, and explains when to try switching between Wi-Fi, mobile data, or another network.
First, determine whether the issue is with the node or your local network
A failed v2rayNG connection doesn’t necessarily mean the app is broken. Common causes include an unavailable node, an outdated subscription, restrictions on your mobile network, an incorrect system time, or DNS issues. Rather than repeatedly uninstalling the app or changing transport settings at random, troubleshoot in this order:
- Open v2rayNG and confirm that the correct node is selected and the switch in the lower-right corner is on.
- Tap the menu in the upper-right corner and select “Test all configurations for a real connection” or a similar test option. Check whether all nodes time out.
- Update your subscription: go to the subscription settings, update it manually, then select a node again.
- Check your phone’s time settings and enable “Set time automatically” and “Set time zone automatically.” An incorrect time can cause a TLS handshake to fail.
- Try other nodes in the same subscription, prioritizing those with lower latency that have worked recently.
If only one node is unavailable, it’s likely temporarily down for maintenance or no longer working. If none of the nodes connect, continue by checking your network environment.
When to switch networks
Switching networks is a low-risk step: it won’t affect your phone’s system or change your node settings. Try it first in these situations:
- You can’t connect on your company, school, or hotel Wi-Fi, but mobile data works.
- The connection keeps showing errors such as timeout, EOF, connection refused, or TLS handshake timeout.
- The same node worked yesterday, but today none of the nodes work on your current Wi-Fi.
- You can browse domestic websites normally, but the real connection test fails for all v2rayNG nodes.
It’s simple: close v2rayNG, disconnect from Wi-Fi, switch to mobile data, and try connecting again. If you were already using mobile data, try your home Wi-Fi instead. If it works as soon as you switch, the issue is likely with your original network’s internet gateway, routing policy, or a temporary restriction imposed by your carrier.
Low-risk troubleshooting steps
To avoid accidentally changing your configuration, follow these steps in order:
- Reconnect: Turn off the v2rayNG switch, wait 5 seconds, then turn it back on.
- Update your subscription or re-import the subscription link to make sure your node list isn’t outdated. This site also provides free nodes you can use to check whether the issue is with your original subscription.
- Try another node, preferably one in a different region or using a different protocol, such as VLESS, VMess, or Trojan.
- Switch networks: test both Wi-Fi and mobile data, and restart your router if necessary.
- Check your app settings: make sure v2rayNG isn’t restricted by battery optimization or background activity limits, which could cause it to disconnect when your screen is locked.
If you use another client, such as Clash or sing-box, you can cross-check the issue in the same way: update the subscription, try another node, and switch networks.
What if you still can’t connect?
If switching networks, trying another node, and updating your subscription don’t help, check the v2rayNG logs. A timeout usually points to a network issue or an unreachable node. Errors mentioning certificate, TLS, or handshake may be related to the time, domain name, or node configuration. A proxy closed error may mean the node is unavailable. Unless you’re an advanced user, don’t change the port, UUID, or encryption method manually—these must match the details provided by the node provider.
In short, if v2rayNG won’t connect, start by updating your subscription, switching nodes, correcting the time, and switching networks. If changing networks gets you connected again, the client itself is probably fine. You can continue using a stable network or wait for your original network to recover.