What should you do if v2rayNG starts but you can’t open webpages, node tests time out, or only your browser can’t access the internet? This article walks you through checking nodes, Android VPN settings, your exit IP, DNS, and browser settings to help identify the source of the problem. A key icon only means the VPN is running; it does not mean the node is working. Menu names may vary slightly between versions.
1. Check the node and your phone’s network
- Turn off v2rayNG and use your browser to visit a site that normally works. If that fails too, first check your Wi-Fi or mobile data connection, or sign in to the network if required.
- Turn on automatic time setting in your system settings. An incorrect time can interfere with TLS verification. Then install or update v2rayNG from a trusted source, and avoid unofficial modified versions.
- Select the configuration you want to use in the node list, start the connection, and allow Android’s VPN request. Pause any other VPNs, firewalls, or ad blockers that use a local VPN to avoid conflicts.
- If you use a subscription, update it and check for any update errors. A successful import does not mean the nodes are still working; free nodes can also stop working, and nodes provided on this site need to be tested in practice too.
- Run a connection or real connection test on the selected node, then compare the results with another node. If needed, switch between Wi-Fi and mobile data. Don’t rely on latency alone to determine whether browsing will work.
2. Check proxy mode and your exit IP
If node tests succeed but some websites won’t open, the issue may be related to routing rules or per-app proxy settings. Temporarily switch to the client’s global proxy routing mode and check whether your browser is excluded from the VPN. If “Proxy only selected apps” is enabled, make sure your browser is selected.
Before and after connecting, compare your exit IP using the same IP lookup page. If the exit IP hasn’t changed, the node may still be working; the lookup traffic may simply be going direct. Caching and differences between IPv4 and IPv6 routes can also affect the result, so check the logs and multiple webpages as well. When you’re done troubleshooting, restore a suitable routing mode to avoid unnecessary data usage.
3. Check DNS if domains won’t load
If the connection test succeeds but a webpage says “Server not found” or “DNS lookup failed,” check DNS first. Note your current settings, then temporarily change Android’s “Private DNS” setting from a custom hostname to Automatic and reconnect to test. You can also temporarily disable any DNS filtering tools on your network.
Next, check whether the DNS settings in v2rayNG have been changed. If you’re unsure what an option does, refer to the documentation for your current version and restore reasonable default settings. Don’t change several settings at once. Change one setting at a time and test again so you can tell which change helped. Avoid repeatedly trying unfamiliar DNS addresses, and don’t disable certificate verification to bypass errors.
4. What if only the browser has problems?
If other apps work normally, first try opening the page in a private browsing window, then compare the results in another browser. Check whether the browser has its own proxy settings, filtering extensions, or custom “Secure DNS” settings; these can make the browser use a different DNS resolution path. You can temporarily restore the defaults to test, but there’s no need to leave security features disabled.
If only one website is affected, the site itself may be down, your sign-in session may have expired, or the site may restrict shared exit IPs. Don’t assume that v2rayNG as a whole has stopped working. Try clearing that site’s cache and cookies rather than immediately deleting all your browsing history.
5. Check the logs if the problem persists
Open the client’s logs, reconnect, and try to visit the page that failed. “timeout” usually points to a connection issue or an unresponsive remote server; “lookup” or other DNS-related messages indicate a resolution problem; and “TLS” or “certificate” errors mean you should check the time, node domain, and configuration. Error messages are clues, not definitive diagnoses. When asking for help, include your client version, network type, and steps to reproduce the problem, and hide sensitive information such as subscription links, UUIDs, and passwords.