This article addresses the common question, “What should I do if v2rayNG won’t connect?” It walks through browser, DNS, server route, and client settings in order of increasing risk. There’s no need to change low-level system settings or set up your own server, so it’s suitable for everyday Android users to follow.
1. First check whether the problem is with your browser or app
Often, v2rayNG shows that it’s connected, but webpages won’t load. That doesn’t necessarily mean the server is down. Try a few simple tests on the same network first to avoid repeatedly deleting your configuration right away.
- Open a browser and visit one domestic website and one website that requires a proxy. Check whether none of them load or only some of them.
- Try another browser—for example, test any two of your system browser, Chrome, or Firefox—to rule out issues caused by the browser cache or extensions.
- Make sure the current configuration is enabled in v2rayNG and that the VPN icon appears in your phone’s notification bar.
- Toggle airplane mode off and on, or switch between Wi-Fi and mobile data, to rule out a temporary network issue.
If only one app can’t connect to the internet, check whether the system has restricted its background network access or whether it’s excluded from per-app proxying in v2rayNG.
2. Check DNS: a key step when you can connect but webpages won’t load
DNS issues often show up as being able to connect to Telegram but not open webpages, or seeing a browser error that says the domain name can’t be resolved. Open v2rayNG settings. Don’t change everything at once; focus on the DNS-related options.
- Make sure you haven’t entered an obviously incorrect custom DNS address.
- If you’ve changed the DNS settings before, restore the defaults and reconnect.
- Turn off “Proxy mode only” and try again to see whether routing rules are causing the issue.
- Clear your browser cache, then test again in a new incognito window.
If you’re using a subscription link, update the subscription first, then try a different server. You can also use the free servers provided on this site for comparison, but free routes are affected by network conditions and aren’t guaranteed to work every time.
3. Check whether the route or server configuration is no longer valid
The most common reasons v2rayNG fails to connect are an expired server, an outdated subscription, an incorrect system time, or mismatched protocol parameters. Everyday users can try these steps in order:
- Tap the menu in the upper-right corner, select Update subscription, and wait for the server list to refresh.
- Try two or three servers in different regions or using different protocols. Don’t keep retrying the same one.
- Check your phone’s system time and enable “Set date and time automatically.”
- Long-press a server and select “Test real connection” or “Test latency.” A latency result of -1 doesn’t always mean it’s unusable, but repeated failures usually indicate that the route is unreachable.
- If you imported the configuration manually, copy the entire vmess, vless, trojan, or ss link again to make sure no characters are missing.
Keep in mind that even one mismatch in the protocol, port, UUID, encryption method, or transport layer can make a configuration appear to import successfully but still fail to connect. Everyday users shouldn’t guess the parameters manually; use a subscription or import from a QR code instead.
4. Low-risk ways to reset the client
If none of the above works, try a light reset: first export your usable servers from v2rayNG or take screenshots of them, then clear the app cache. Don’t rush to clear all app data. Next, restart your phone, reimport the subscription, and connect again. If it still fails, try uninstalling and reinstalling the latest version of v2rayNG.
When troubleshooting, change only one setting at a time and keep track of what you’ve changed. If it says “Connected” but there’s no internet, check DNS and routing first. If the connection fails outright, try another route and update the subscription. If you get an error after importing, first check whether the link is complete. Following these steps in order usually helps you quickly determine whether the problem is with the browser, DNS, network, or server itself.