What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: browsers, system VPN settings, subscription servers, and DNS. It helps you tell the difference between the client failing to start and connecting successfully but being unable to open webpages. The steps favor reversible changes, so there’s no need to reinstall the app, clear its configuration, or change complicated settings.
1. Check your basic network and VPN status
- Temporarily stop v2rayNG and open a website you can normally access directly. If that doesn’t work either, check your Wi-Fi, mobile data, or any login page required by the public network.
- Start the connection again. Watch for an Android VPN authorization prompt, and check for the VPN icon in the status bar. The icon means the system tunnel has been established; it doesn’t guarantee that the server is working.
- Turn off other VPNs, accelerators, or ad-blocking tools that use a local VPN, as they may compete for the system VPN connection. If you have an always-on VPN enabled, check whether it’s set to use another app.
- If the connection drops frequently, check whether the system is restricting v2rayNG’s background activity. You can temporarily allow background activity to compare results; there’s no need to disable all battery-saving features at once.
Change one setting at a time and note its original value before making changes. If a change doesn’t help, restore the original setting. This prevents multiple changes from piling up and making the cause difficult to identify.
2. If webpages won’t open, check whether the problem is browser-specific
Try opening the same URL in another browser, then test a different website. If only one browser fails, check its settings first rather than immediately switching all your servers.
- Check whether the browser has custom “Secure DNS” enabled. If a specific DNS service is selected, temporarily switch to the default or automatic setting and test again. Restore it afterward if needed.
- Check v2rayNG’s per-app proxy settings to make sure the browser hasn’t been excluded. Also confirm whether the selected mode proxies the apps you select or bypasses them.
- If other apps work but one website doesn’t, try opening it in a private window for comparison. Don’t ignore certificate warnings or install unknown certificates just to access a webpage.
3. Check whether your subscription and servers are still working
Update your subscription once in the client and check for an update error or an empty result. An update failure may mean the subscription URL is temporarily unreachable; it doesn’t mean that all your saved servers have stopped working. Switch to another server from a source you trust, reconnect, and try opening a webpage.
Latency tests are only a guide and don’t replace testing a webpage. An error during a test doesn’t necessarily mean the server is completely unavailable. Compare Wi-Fi and mobile data: if the problem occurs on only one network, the network environment is a more likely cause. Free servers may stop working. When using servers from this site or another source, check when they were last updated rather than repeatedly testing the same outdated server.
4. Check DNS and error logs as a last step
If multiple apps can’t open domain names and the logs repeatedly show resolution failures or errors related to DNS or lookup, check your DNS settings. Android’s “Private DNS” and a browser’s “Secure DNS” are separate settings. If you manually set a Private DNS server, try switching it to automatic first. Don’t change multiple DNS settings in the client at the same time.
A timeout in the logs usually means the connection timed out, but that alone doesn’t identify the cause. For certificate or TLS errors, first check your phone’s date and time and make sure the server details are complete. Don’t bypass errors by turning off certificate verification. If the issue persists, note the client version, network type, and when the error occurred. Before sharing logs, redact sensitive information such as your subscription URL, UUID, and password.