This article addresses the common question, “What should I do if v2rayNG won’t connect?” It avoids complex server-side settings and guides you through checks in a low-risk order—from nodes and subscriptions to the client and your phone’s network environment—to help determine whether the issue is caused by your configuration, an unavailable node, or restrictions on your current network.
1. First, make sure the basic settings are correct
If v2rayNG fails to connect, don’t immediately reinstall it repeatedly or make random changes to the settings. Many issues are simply caused by an expired node, an outdated subscription, or the system proxy not being enabled. Start with these checks:
- Open v2rayNG and make sure a node is selected. It should be highlighted or marked with a check on the left.
- Tap “Update subscription” or “Update from subscription” in the top-right corner, then wait for the list to refresh.
- Open the node’s edit page and make sure fields such as the address, port, UUID, and transport protocol haven’t been accidentally deleted.
- Return to the home screen and tap the connect button in the bottom-right corner. Check whether a VPN icon appears in the notification bar.
- Open a browser and visit a familiar website to test the connection. Don’t rely on speed test results alone.
If you’re using the free nodes provided on this site, update the subscription before testing. Free node availability can change, so one unavailable node doesn’t mean the client is broken.
2. Rule out an unavailable node by switching nodes
The most common causes are an unavailable node or congestion on the current node. The low-risk approach is to switch nodes without changing advanced settings. Try 3 to 5 nodes in different regions or using different protocols. After connecting to each one, wait about 10 seconds before opening a webpage.
If all nodes time out or show errors such as “TLS handshake failed” or “connection refused,” the entire subscription may be unavailable, or your network may be blocking the connection. Don’t change routing rules, camouflage domains, or underlying transport settings at random, or you could disrupt a configuration that was working correctly.
3. When to try a different network
If you’ve updated the subscription, tried several nodes, and restarted v2rayNG but still can’t connect to any of them, consider switching networks. This means switching from Wi-Fi to mobile data, or from mobile data to another Wi-Fi network, to see whether the issue is caused by restrictions on your local network.
- If all the same nodes fail over Wi-Fi but work over mobile data, the problem is likely a Wi-Fi restriction or a DNS issue.
- If they fail over both mobile data and Wi-Fi, the issue is more likely related to the nodes, subscription, or client configuration.
- If only certain apps don’t work, check per-app proxy settings, system VPN permissions, and battery restrictions.
- If the connection succeeds but webpages won’t load, check the routing mode, DNS, and browser cache first.
Low-risk tip: Only switch networks to test the connection. Don’t disable your phone’s security settings, install modified client apps from untrusted sources, or grant unrelated permissions.
4. Safe troubleshooting steps for the client
If switching networks doesn’t help, continue troubleshooting v2rayNG itself. First, update to a recent version from an official source. Then clear the old subscription and reimport the subscription link, or test by copying a single node link. After importing, check whether a node list appears. If the list is empty, the subscription link is usually invalid or wasn’t copied in full.
You can also check your Android system settings: allow v2rayNG to use VPN permissions, and remove any extreme battery-saving restrictions for v2rayNG. If “Always-on VPN” or another VPN app is enabled, disable any conflicting settings first. Don’t run multiple VPN or proxy clients at the same time, as this can cause the connection to appear active while the internet remains unavailable.
5. Quick troubleshooting summary
Keep this order in mind: update the subscription, switch nodes, switch networks, and then check the client. If switching networks fixes the issue right away, focus on your current Wi-Fi or mobile carrier network. If none of these steps help, focus on getting a working subscription or reimporting the nodes. Following this order can usually help you identify why v2rayNG won’t connect without having to tinker with advanced settings.