This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on low-risk troubleshooting: no changes to core system settings, no flashing your phone, and no installing random certificates. Start by checking your browser, DNS, server routes, and client configuration step by step. These instructions are suitable for everyday Android users.
1. First, identify where the problem is
If v2rayNG won’t connect, the server may not be the problem. Browser cache, DNS resolution, the system proxy, or an incorrect clock could also be to blame. Start with a simple check: open v2rayNG, select your current server, and tap Test in the top-right corner or connect directly. Then check whether a key icon appears in the status bar. If it does but webpages won’t load, check your browser and DNS first. If it doesn’t appear or disappears shortly after, check the server and configuration.
- Check that your phone’s network is working: turn off v2rayNG and open a domestic website using your regular connection.
- Check that the time is correct: set the system time to “Set date and time automatically.”
- Make sure you’re only running one proxy app: don’t run Clash, sing-box, or another VPN at the same time.
- Test on both Wi-Fi and mobile data to rule out restrictions on your current network.
2. Browser checks: try another page, then clear the cache
Many users think the connection has failed when the real issue is the browser cache or a temporarily inaccessible website. After connecting with v2rayNG, test more than one webpage. Try different types of sites, such as a search engine, a video site, and developer documentation. If only one particular site won’t open, it may be restricting access or having compatibility issues with the route.
Try these steps in order: test in your browser’s private browsing mode; turn off features such as “data saver,” “Secure DNS,” and built-in proxies; clear the browser cache and try again. If you’re using a locally developed browser, you can also temporarily switch to Chrome, Firefox, or Edge for testing. These steps are low-risk and won’t affect your v2rayNG configuration.
3. Check DNS: focus here if you’re connected but webpages won’t open
If v2rayNG shows that you’re connected but your browser reports that it can’t resolve a domain, shows DNS_PROBE_FINISHED, or says the server can’t be found, DNS may be the cause. In v2rayNG settings, check whether options such as “Bypass LAN and mainland China addresses” are enabled. If you’re unfamiliar with routing rules, start with the defaults or commonly used rules. Don’t import complicated rules from unknown sources.
- Turn off Private DNS in Android settings, then reconnect and test again.
- Switch v2rayNG routing modes—for example, from global mode to rule mode, or vice versa—and test again.
- Restart v2rayNG, and force-stop it from Android’s app settings to make sure it’s fully closed in the background.
- Reset your phone’s network connection: turn Airplane mode on for 10 seconds, then turn it off and reconnect.
Note: Don’t install apps that claim to “repair DNS certificates” or modify your hosts file. It’s easy to make things worse if you’re not sure what you’re changing.
4. Check the routes and subscription: servers going offline is the most common cause
If v2rayNG disconnects soon after connecting or a latency test fails, the server may be unavailable. In your subscription group, tap Update subscription, then test two or three routes in different regions or using different protocols. This site collects some free server resources, but their availability can fluctuate. It’s a good idea to keep several backup servers instead of relying on just one.
After importing a server, check the basic details: the protocol should be VLESS, VMess, Trojan, or another supported option; the address, port, UUID, and transport settings should all be present; and don’t make random changes to fields such as TLS, Reality, or the WS path. If you imported the server from a link, make sure the link wasn’t truncated by your messaging app. If you see “Invalid configuration,” deleting the server and importing it again is usually safer than editing each setting individually.
5. Low-risk recovery steps if it still doesn’t work
- Back up any working subscription links or server QR codes.
- Update the subscription in v2rayNG and delete any obviously inactive servers.
- Clear the v2rayNG cache instead of clearing all app data.
- Upgrade to a stable release of v2rayNG. Avoid modified versions from unknown sources.
- Restart your phone, then test with v2rayNG as the only proxy app running.
In short, if v2rayNG won’t connect, troubleshoot in this order: check whether your network is working, whether your browser is behaving normally, whether DNS is resolving, whether the server is available, and whether the configuration is complete. This won’t disrupt your system settings and should help you pinpoint most problems quickly. If all your servers fail, try a different subscription source or wait for the routes to come back online.