What should you do when v2rayNG won’t connect? This guide walks through checks for your browser, system permissions, DNS, and node connections to help you tell the difference between “the client is running, but webpages won’t load” and “the node itself can’t connect.” The steps prioritize changes you can easily undo. There’s no need to reset your phone, disable security protections, or change server settings.
1. Check the connection status and keep your existing settings
Before you start, note your current node, routing mode, and DNS settings. Change only one thing at a time so you can undo it if needed. Don’t start by clearing the app’s data or deleting all your subscriptions, or you could lose settings that were working. Menu names may vary slightly between versions, so refer to what you see on your screen.
- With v2rayNG disconnected, check whether you can open domestic websites on your phone. If you can’t, troubleshoot Wi-Fi sign-in, your mobile data balance, or other basic network issues first.
- Open v2rayNG, select a node, and connect. The first time you connect, you’ll need to approve Android’s VPN connection request.
- Check whether the VPN icon appears in the status bar, then run the client’s connection test. Treat the latency result as a rough guide and verify by opening a webpage.
- If another VPN, accelerator, or filtering tool that uses a local VPN is running, pause it first to prevent it from taking over the system’s VPN connection.
2. If webpages won’t load in just one browser, check the browser and routing
If other apps can connect to the internet but one browser can’t, try opening the same page in another browser, then test it in an incognito window. If it works in incognito, you can clear just that website’s cache and site data; there’s no need to delete all your browsing history.
Check v2rayNG’s per-app proxy settings to make sure the browser hasn’t been excluded. Also check the routing mode in case traffic to the website is mistakenly going direct. You can temporarily switch to global proxy mode for comparison, then restore your original mode afterward. If only one website is unavailable, it may be down for maintenance or restricting access based on your exit IP. Don’t assume all your nodes are down.
3. Check DNS: restore automatic settings first, then compare
If webpages show “server not found” or a DNS resolution error while some apps still work, check your DNS settings. In Android’s network settings, find “Private DNS.” If you previously entered a provider’s address manually, note it down, then temporarily switch to “Automatic” and test again. Avoid entering DNS addresses from untrusted sources.
Your browser may also have its own “Secure DNS” setting. Temporarily set it to use your current service provider or the system setting, then restart the browser and try again. If you’ve changed DNS in v2rayNG, take a screenshot first, then restore a setting you know works. Change only one DNS setting at a time so you can tell which change made a difference.
4. Switch networks and nodes to check for connection issues
Keep the same node and test over both Wi-Fi and mobile data, keeping an eye on data usage. If it fails on only one network, the network’s restrictions or connection quality may be the cause. If it fails on both, try a node on a different route. If you have a subscription, update it first. Once the update succeeds, select a node again—but a successful update doesn’t guarantee that the node is online.
Free nodes may stop working or become temporarily congested. Whether you’re using free nodes from this site or another source, check when they were last updated and make sure the configuration is complete. Don’t keep importing the same dead link. Log messages such as timeouts, DNS resolution failures, or certificate errors can help narrow down the cause. If you see a certificate error, check your phone’s date and time. Don’t bypass certificate verification to force a connection.
If the issue persists, contact your node provider with your client version, network type, error message, and the tests you’ve tried. Before sharing a screenshot, hide your subscription link, UUID, and other credentials; don’t post your full configuration.