What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting issues such as webpages not loading after startup, latency tests timing out, or only some apps working. Check the node, system proxy, IP, DNS, and browser settings step by step. First determine the scope of the problem, then change settings to avoid making several changes at once and losing track of the cause.
I. First, check that your network and node are working
- Close v2rayNG and open a website you can normally access directly. If it won’t load either, first check your Wi-Fi, mobile data, or network login requirements.
- Set your phone to use the automatic date and time. An incorrect clock can interfere with TLS certificate verification and cause connection failures.
- Update your subscription and select a node again. Check that the imported configuration is complete. If the link came from a free-node page, keep in mind that availability can change, so an old link may no longer work.
- Start the connection and accept the Android VPN permission prompt. If the VPN icon doesn’t appear, check whether another VPN, ad blocker, or packet-capture app is using the system VPN.
- Run a connection test for the selected node, then open a webpage to verify it works. A latency reading does not guarantee that webpages will load, and a single timeout is not enough to conclude that a node is unavailable.
II. Check proxy mode and app routing
If v2rayNG shows as connected but only some apps won’t open, first check its per-app proxy settings. Make sure your browser isn’t excluded, and that you haven’t selected the opposite of what you intended under “Proxy only selected apps” or “Bypass selected apps.” Menu names may vary by version, so use the options shown in your current interface.
Temporarily switch to global proxy mode for comparison. If it works globally but not in rule mode, check the routing rules first instead of repeatedly switching nodes. Restore your usual mode after testing. Also close other proxy tools and, if necessary, stop and restart the connection.
III. What do IP and DNS each affect?
The node server address determines where the client connects, while the exit IP is the apparent source of your traffic to websites. A website’s region restriction or verification prompt does not mean the tunnel is disconnected. After connecting, use a trusted IP lookup site to see whether your exit IP has changed. If split tunneling is enabled, however, that site may connect directly, so check your proxy mode as well.
DNS translates domain names into addresses. If the logs repeatedly show domain resolution failures, first check that the node’s domain name is complete. Then check whether your phone’s “Private DNS” is set to a custom service that can’t be reached on your current network. You can temporarily switch it to automatic and test again. Note the result before deciding whether to restore the previous setting.
If the client offers DNS settings, keep the defaults for now rather than copying an unverified combination. Do not disable certificate verification to fix connection problems. Instead, check your system time and node settings, or contact the node provider.
IV. Rule out browser issues and check the logs
If other apps work and only the browser has problems, open the same website in a private window, then try another browser. Check the browser’s secure DNS, built-in proxy, and extension settings. Private browsing can help rule out some cache or extension issues, but it cannot fix the node itself.
Finally, check the v2rayNG logs: for DNS resolution errors, check DNS first; for connection timeouts, compare nodes and networks; for certificate errors, check the time and configuration. Change only one setting at a time, then compare results across Wi-Fi, mobile data, or another node. If the problem persists, note the client and system versions and the error message. Before sharing screenshots, be sure to hide sensitive information such as subscription URLs and UUIDs.