v2rayNG shows that it’s connected, but webpages won’t load, or node tests keep timing out. What should you do? This guide walks you through troubleshooting your network, nodes, routing, DNS, and browser environment to help you distinguish connection issues from restrictions imposed by the website itself. The VPN icon only indicates that the local proxy service has started; it does not mean the node is necessarily working.
1. Check that your network and node are working
- Stop v2rayNG and check whether regular websites load. If your basic internet connection is also unavailable, complete the Wi-Fi sign-in process or switch to mobile data and try again.
- Turn off other VPNs, proxies, and network-filtering apps to prevent them from competing for Android’s VPN connection. Restart v2rayNG and allow the VPN connection request when prompted by the system.
- Select a node and run the connection test provided by the app; the steps may vary between versions. Treat latency results as a guide, and also try opening a webpage.
- Update your subscription and check for any update errors. If you use a single share link, import it again and verify the address, port, and protocol settings against the source. Don’t change them arbitrarily.
- Test another trusted node. If only one node fails on the same network, the node may be down or its route may be experiencing problems. If all nodes fail, check your device settings.
Our free nodes can be used for comparison testing, but their availability may change. Do not share your subscription link, node password, or screenshots of your complete configuration publicly. If you ask others for help, hide sensitive information first.
2. Check proxy mode and DNS
In v2rayNG settings, confirm that you’re using VPN mode rather than local proxy mode, which is intended for manual connections by other apps. If per-app proxying is enabled, check that your browser isn’t excluded. If only selected apps are proxied, add the apps you need to the list.
To see whether routing rules are the problem, temporarily switch to global proxy mode, reconnect, and test again. If global mode works but split tunneling doesn’t, check whether the rules match the target website. Restore your usual mode after testing.
If the logs repeatedly show domain resolution failures, check your DNS settings. Android Private DNS, your browser’s Secure DNS, and the client’s DNS settings may use different resolution paths. First note your current settings, then restore the defaults or temporarily disable custom DNS settings one at a time, reconnecting and testing after each change. Don’t change your node, DNS, and routing settings all at once, or it will be difficult to tell which change made a difference.
3. Distinguish exit IP issues from browser issues
After connecting, use a trusted IP lookup page to check whether your exit IP has changed. If it still shows your local network’s IP, check whether your browser is using the proxy and whether the lookup page is set to bypass it. If your exit IP has changed but a particular website won’t load, the issue may be related to exit IP restrictions, regional restrictions, or a website outage—not a v2rayNG connection failure.
Try another browser or an incognito window. If needed, clear the target website’s cache and cookies. Incognito mode won’t change your exit IP; it’s only useful for troubleshooting certain session issues. If you see a certificate error, first check that your phone’s date and time are correct. Never ignore certificate warnings just to access a website.
4. Check the logs if the problem persists
Clear the old logs, reconnect once, and check the new error messages. A timeout may indicate a routing issue or an unreachable server. For DNS resolution errors, first check the resolution path. For TLS or certificate errors, verify the time, node settings, and client compatibility. Don’t diagnose the issue based on a single error message; consider the results of testing a different network and node as well.
Finally, update to the stable version from the project’s official release channel, then try again after backing up your configuration. If the connection drops only when the screen is locked, check the system’s background activity and battery optimization restrictions. When asking for help, include the client version, network type, and sanitized logs to make it easier to pinpoint the problem.