What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting your browser, system settings, DNS, and server routes to help you tell the difference between traffic not being routed through the proxy and the server itself being unavailable. Start with steps that are easy to undo; there’s no need to clear your configuration or reinstall the app right away.
1. First, check your network and VPN connection
- Stop v2rayNG and make sure your phone can open commonly used websites. If it can’t, first check for Wi-Fi sign-in requirements, mobile data issues, or an unpaid bill.
- Restart v2rayNG, make sure the desired server is selected, and allow the VPN connection request prompted by Android. A VPN icon in the notification bar only means the tunnel has started; it doesn’t confirm that the server is working.
- Pause other VPNs, ad blockers that use Android’s local VPN mode, and packet-capture tools. These apps generally can’t route connections at the same time as v2rayNG.
- Check that your system date, time, and time zone are set to sync automatically. A significantly incorrect clock can cause encrypted connections or certificate checks to fail.
Change only one setting at a time, and take a screenshot of its original value before changing it. Test the result before deciding whether to keep or revert the change, so you don’t alter several variables at once.
2. If websites won’t open in your browser, check the app and routing rules first
Test two different websites, then try another browser or an incognito window. If only one website has a problem, don’t assume the server is down. If only one browser is affected, check its Secure DNS, custom proxy, and extension settings. Temporarily restore the defaults and test again.
In v2rayNG, check per-app proxy settings: make sure the browser isn’t excluded, and that it’s selected if “Proxy only selected apps” is enabled. Then check the routing mode. If needed, briefly switch to global proxy mode as a test, and restore your original routing mode afterward. Global mode is a troubleshooting step, not a setting you need to keep enabled.
3. How to check DNS without making things more complicated
If the logs repeatedly show domain resolution failures or DNS timeouts, first check Android’s “Private DNS” setting. If you’ve configured a custom provider, temporarily switch it to “Automatic” and test again. Menu names may vary between phones. Also check Secure DNS in your browser separately to avoid conflicts between the two settings.
Next, check whether custom DNS is enabled in v2rayNG. Note the current value, then restore the default or use a trusted DNS configuration as recommended for your version. Don’t copy addresses from unverified sources. Don’t disable TLS certificate verification or enable “Allow insecure connections” as a troubleshooting step. If the logs don’t indicate a resolution error, check the server route instead of repeatedly changing DNS settings.
4. Check your subscription, server, and network route
- Manually update your subscription and check whether the update succeeds. Free servers may stop working or change, and a successful subscription update doesn’t guarantee that every route in it is available.
- Test another server from a trusted source. Latency results can be a useful clue, but actual access is what matters.
- Test over both Wi-Fi and mobile data. If the connection fails on only one network, check that network’s restrictions or compatibility.
- Make sure the client comes from the project’s official distribution channel, and read the release notes. Back up your configuration before updating, and don’t install modified versions from unknown sources.
If you still can’t connect, note the client version, network type, and relevant error messages, then contact your subscription provider. Before sharing logs or screenshots, be sure to hide your subscription link, UUID, password, and personal information. Test this site’s free servers using the same steps; availability isn’t guaranteed.