This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on your browser, DNS, server routes, and client settings, and provides a low-risk troubleshooting checklist. You don’t need to change any low-level phone system settings or set up your own server—just follow the steps in order.
1. First, identify where the problem is
In many cases, v2rayNG itself isn’t the problem. It may be caused by browser cache, DNS resolution, an inactive server, or the system proxy not being applied. Start with a simple check: open v2rayNG and tap a server to connect. If the key icon appears at the top, the VPN tunnel is attempting to connect. If you see a timeout, TLS error, EOF, or connection refused message, the server or network is more likely to be the issue.
- Switch networks: try mobile data instead of Wi-Fi, or vice versa.
- Make sure your system time is correct, as an inaccurate clock can affect the TLS handshake.
- Turn off battery saver mode to prevent the system from restricting background network activity.
- Restart v2rayNG and try connecting again.
2. Check your browser: rule out “connected, but webpages won’t load”
If v2rayNG shows that it’s connected but your browser won’t load webpages, don’t rush to delete your configuration. Try the following checks first:
- Test with another browser, such as Chrome, Edge, Firefox, or your system browser.
- Clear your browser cache, especially if you’ve been using the same browser for a long time.
- Turn off built-in browser features such as “Secure DNS,” “Data Saver,” or “Proxy acceleration.”
- Open a webpage in incognito mode to rule out interference from extensions, cache, and cookies.
Some browsers manage DNS or proxy settings themselves, which can conflict with v2rayNG. The low-risk approach is to turn off these enhanced features first, then test with common websites. Avoid changing advanced settings right away.
3. DNS settings: start with the client’s built-in options
DNS issues can cause symptoms such as a connected server but inaccessible domains, or IP-based test websites loading while regular websites don’t. In v2rayNG, open “Settings” and check the DNS options. Most users should stick with the default configuration or enable the remote DNS recommended by the client. Don’t enter DNS addresses from untrusted sources.
If you’ve changed your DNS settings before, restore the defaults and test the connection again. If you’re using a subscription, update it and select a server again; sometimes the configuration will include a more suitable DNS policy. Remember: when troubleshooting DNS, make as few changes as possible, change one setting at a time, and test immediately after each change.
4. Check the server route: inactive servers are the most common cause
Free servers and public subscriptions often become congested, blocked, or affected by configuration changes. This site compiles some free server resources, but any free route can be unstable, so compare several servers as part of your troubleshooting.
- On the v2rayNG home screen, long-press the subscription group and select “Update subscription.”
- Try 3 to 5 servers in different regions or using different protocols.
- Use “Test all configurations for real connection” or a similar feature to check the results.
- Choose servers with normal latency that pass the real connection test.
If all servers fail, your local network may be restricted, the subscription link may have expired, or the client version may be outdated. In that case, update v2rayNG to a newer version and import the subscription again.
5. Review the client settings and import method
If you imported a vmess, vless, or trojan link manually, make sure you copied it in full and that it contains no extra spaces or line breaks. If importing from a QR code fails, try importing from the clipboard instead. Subscriptions are usually more convenient for most users, since you can update all server settings at once when they change.
- Make sure you haven’t changed the routing mode by mistake. Most users can start with the default mode or use global mode for testing.
- Check that advanced options such as “Allow connections from LAN” haven’t been enabled by mistake.
- If per-app proxying is enabled, make sure your browser is selected.
- Before uninstalling and reinstalling the app, back up your subscription link to avoid losing your configuration.
Finally, troubleshoot in this order: switch networks, try another browser, restore DNS defaults, update the subscription, try another server, and update the client. This is the lowest-risk approach and makes it easiest to pinpoint the issue. If v2rayNG won’t connect, don’t change a bunch of settings at once; change only one setting at a time so you can tell which step fixed the problem.