What should you do if v2rayNG won’t connect? This guide helps you distinguish between a dead node, traffic not being routed through the proxy, DNS resolution issues, and browser-related problems. Check the items in order and change only one setting at a time to avoid making it impossible to identify the cause after switching several settings at once.
1. First, check whether your network and node are working
- Close v2rayNG and use your browser to visit a site that normally works without a proxy. If it won’t load either, first check your Wi-Fi, mobile data, or network sign-in requirements.
- Check your phone’s date, time, and time zone. We recommend enabling automatic settings. An incorrect time can cause certificate verification to fail.
- Update your subscription and check for errors, then select a node and start it. If you use free nodes from sources such as freevpn-x.com, pay attention to when they were published. Successfully importing a node doesn’t mean it’s still working.
- Check for client updates through the project’s official release channels. Back up your configuration before installing an update over the existing app, and don’t install modified versions from unknown sources.
Latency test results don’t necessarily reflect whether web pages will actually load. Some tests may time out even though the proxy still works. Conversely, a reported latency doesn’t prove that a particular site will open. Use actual browsing results and logs to assess the issue.
2. It says connected, but no web pages will open
After starting the connection, confirm that Android has granted VPN permission and that a VPN connection indicator appears in the system. Other VPNs, accelerators, or filtering tools that use a local VPN on your phone may conflict with v2rayNG. Turn them off while testing.
Check v2rayNG’s per-app proxy settings and make sure your browser isn’t excluded. Then temporarily switch to global proxy mode for testing. If global mode works but your original routing mode doesn’t, focus on the routing rules. Restore your preferred mode after testing.
Don’t assume your phone’s IP has been blocked just because the connection failed. Compare Wi-Fi and mobile data. If it fails only on one network, the cause is more likely related to that network’s restrictions or connection path. If switching nodes immediately fixes the issue, check the original node rather than repeatedly changing your phone’s settings.
3. Check whether the problem is DNS or your browser
DNS translates domain names into IP addresses. Open the client logs. If you repeatedly see resolution failures or DNS timeouts, note your current settings, then restore any manually configured DNS to the client’s default and test again. If you’ve set a custom service for Android’s “Private DNS,” temporarily switch it to Automatic to avoid layering multiple settings.
- Only one browser fails: Try another browser or an incognito window, and check the browser’s Secure DNS, proxy extensions, and site cache.
- Your browser works, but a particular app doesn’t: Check whether the app is excluded from the proxy and whether it needs to be fully closed and reopened.
- Only one site won’t open: The site may be down, the exit IP may be restricted, or the site may be applying a login security check. Don’t assume the entire proxy is broken.
Don’t try to diagnose DNS by visiting a site’s IP address directly. Many HTTPS sites rely on the domain name matching the certificate, so failure to open a site by IP doesn’t indicate a problem with the node.
4. What information to keep if the problem persists
Stop the connection, start it again, reproduce the issue once, and then check the logs for that time. For connection timeouts, check the node and network path first; for certificate errors, check the time and node details; for resolution errors, check DNS first. Don’t enable certificate verification bypass just to clear an error.
When asking for help, provide the client version, Android version, network type, scope of the failure, and a redacted error message. Don’t share your subscription link, UUID, password, or a complete node QR code publicly. If multiple nodes fail on two different networks, consider backing up your settings, restoring the client, and rebuilding the configuration one item at a time.