What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in this order: local network → client → browser → DNS → node route. It’s intended for Android users who have imported nodes but can’t open webpages, encounter connection timeouts, or can’t access certain websites. Start with checks you can easily undo. There’s no need to reinstall the app right away, and you shouldn’t change several settings at once.
1. First, check your network and make sure the VPN starts properly
- Stop v2rayNG and try opening a website you can normally access. If it won’t load either, switch between Wi-Fi and mobile data. Public Wi-Fi may require you to sign in through a web page first.
- Restart v2rayNG, tap Connect, and approve Android’s VPN permission prompt. The VPN icon in the status bar only means the tunnel has started; it doesn’t prove that the node is working.
- Temporarily disable any other VPN, firewall, or ad blocker that uses Android’s local VPN mode. Android generally can’t run two of these services at the same time. Re-enable them after testing.
- Check your system date, time, and time zone, and consider enabling automatic settings. An incorrect clock can cause certificate validation to fail. Don’t try to fix this by disabling certificate verification.
Test after each step so you can tell which change helped. If the connection drops only after the screen locks, check battery optimization and background permissions instead of loosening all permissions from the start.
2. If a browser won’t open websites, the node may still be working
Test two different websites, then try opening the same page in another browser. If only one browser has the problem, try an incognito window to rule out cache, extensions, or an old session. Don’t immediately clear all app data.
Also check v2rayNG’s routing settings. If you’re using per-app proxying, make sure the browser isn’t excluded. You can temporarily switch to a routing mode that sends more traffic through the proxy for comparison, then restore your original setting after testing. Menu names may vary between versions.
The browser’s “Secure DNS” and Android’s “Private DNS” can also affect the results. Note your original settings, then test one change at a time: for example, temporarily change manually configured Private DNS to “Automatic,” or temporarily turn off Secure DNS in the browser. Don’t change both at once, and don’t enter DNS addresses from untrusted sources.
3. Use the logs to distinguish DNS issues from connection problems
Open the v2rayNG logs, connect, visit a webpage once, and check for any new errors. Messages containing “lookup,” “DNS,” or a domain name resolution timeout may point to a DNS issue. A “timeout” could also mean the network or route is unreachable. Certificate errors warrant checking the system time, node address, and configuration. A single error message isn’t enough to identify the cause.
- If domain resolution errors keep appearing, first restore the client’s default DNS settings, then compare Wi-Fi and mobile data.
- If the connection keeps timing out, try a node from a trusted source. Don’t judge a route based on a single latency test.
- If you see a certificate or handshake error, check the subscription configuration again. Don’t change the port, transport, or TLS parameters at random.
4. Update the subscription, then cross-check your results
Update the subscription manually and check whether it succeeds. A failed update doesn’t necessarily mean the existing nodes are unusable; the subscription address may simply be temporarily unreachable. When using free nodes from sources such as freevpn-x.com, check the publication date and any notes about availability. Free routes may not always be available.
Finally, isolate the issue by testing the same node on a different network, then a different node on the same network. If the first test works, focus on the original network. If the second works, the original node is the more likely cause. If you still can’t connect, include the client version, the time of the error, and a redacted log when asking for help. Don’t share your subscription link, UUID, or full node QR code publicly.