This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on low-risk troubleshooting: first check your device settings, such as nodes, subscriptions, system time, and proxy mode. Then determine whether you need to switch between Wi-Fi, mobile data, or another network. Avoid repeatedly reinstalling the app or changing settings at random right away.
1. Start with 5 low-risk checks
A failed v2rayNG connection doesn’t necessarily mean the node is down. The cause could also be your local network, system time, or an expired or cached subscription. Check these items in order, and avoid changing several settings at once so you can pinpoint the cause.
- Check that the node is available: Open v2rayNG, long-press the current node, and select “Test real connectivity for all configurations” or a similar option. If multiple nodes time out, continue troubleshooting your network.
- Check whether your subscription is up to date: Go to the subscription settings and tap Update subscription. Free nodes provided by this site may also become unavailable due to maintenance or changes in traffic, so test again after updating.
- Check your phone’s time: A significant system time mismatch can cause TLS handshake failures. We recommend enabling “Set time automatically” and “Set time zone automatically.”
- Check the proxy mode: In v2rayNG settings, make sure VPN mode is enabled. Once a key or VPN icon appears in the status bar, open a browser and test the connection.
- Close conflicting apps: Don’t run other VPNs, accelerators, or proxy apps at the same time. Some security apps may also block VPN connections.
2. When to switch network environments
If node tests keep showing errors such as timeout, connection refused, or TLS handshake timeout, but the same subscription works on another device or over a friend’s network, your current network may be restricting the connection. Switching networks is a low-risk step that won’t damage your configuration.
- Can’t connect over home Wi-Fi? Switch to mobile data and test again.
- Mobile data isn’t working? Try switching between 4G and 5G, or toggle airplane mode to reconnect to the network.
- Can’t connect on a company, school, or public Wi-Fi network? These networks often have firewalls or port restrictions. Try a personal hotspot or home network instead.
- The same node works occasionally but disconnects often? Try another node or a backup connection using a similar protocol. Avoid frequently changing core settings.
3. Follow these steps to restore the connection
Recommended steps: update the subscription → test the node → switch to another node → restart v2rayNG → switch network environments → restart your phone. Test whether a webpage opens after each step to avoid misdiagnosing the problem.
If you’re using a VLESS, VMess, Trojan, or other node, we don’t recommend manually changing fields such as host, path, security, or sni. These parameters must match the server, and incorrect changes could make all connections fail. After importing a subscription, it’s usually safest to keep the default settings.
You can also check the errors in the v2rayNG log: timeout errors are often related to the network or node connectivity; for certificate- or TLS-related errors, check your system time first; for DNS-related errors, try switching networks or enabling the client’s built-in DNS. A longer, more complicated log isn’t necessarily more helpful—just focus on the keywords.
4. What if it still won’t connect?
If it still fails after switching networks and nodes and updating the subscription, try reinstalling the latest version of v2rayNG and reimporting your subscription link or node QR code. Be sure to back up any working subscription addresses first. As a last resort, try a different client, such as Clash Meta or sing-box, to rule out a compatibility issue with v2rayNG.
In short, if v2rayNG won’t connect, start with these safe steps: update your subscription, test the node, check your system time, close conflicting VPN apps, and switch network environments. Don’t change advanced settings blindly, and don’t assume that one failed connection means all your nodes are unavailable.