What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting your network, nodes, proxy mode, DNS, and browser to resolve issues such as web pages not loading after startup, some apps being unable to connect, or latency tests failing. First, distinguish between an “unavailable node” and “traffic not being routed through the proxy.” Don’t start by repeatedly changing settings.
1. Check your network and VPN permissions
- Stop v2rayNG and open a website that you can normally access. If that doesn’t load either, first troubleshoot your Wi-Fi, mobile data, or public network sign-in.
- Check the project’s official release channels for the client version. Back up your subscription URL or configuration before updating to avoid losing it if you uninstall the app.
- Select a node, tap Start, and allow the VPN connection request from Android. The VPN icon in the status bar only indicates that the tunnel has started; it does not mean the node is working.
- Temporarily disable other VPNs, ad blockers that use a local VPN, and any firewalls that might conflict. Android generally can’t run two VPNs at the same time.
- If the connection drops after the screen locks, allow v2rayNG to run in the background in your system settings and check for battery optimization restrictions.
2. Check whether the node or subscription is no longer valid
After updating your subscription, try another node. A successful import only means the client recognized the configuration; it doesn’t prove that the server is online. If importing manually, check that the link was copied in full. Don’t change the address, port, UUID, or TLS-related fields yourself.
A latency test timing out doesn’t necessarily mean you can’t access the internet. Check actual website access and the logs as well. Test methods may vary between versions, and a successful TCP connection doesn’t mean proxy requests will succeed. If only one node fails, try another first. If all nodes fail, check your local network and client. If you’re using this site’s free nodes, pay attention to update notices and don’t assume that old links will remain valid indefinitely.
3. Check your IP, proxy mode, and DNS
The public IP shown on a website is usually the result of your connection, not a direct cause of connection failure. If an IP lookup page shows your local carrier, the request may have gone directly, or your browser may have bypassed the proxy. If it shows a proxy IP, that only confirms that this particular request went through the proxy.
Check your routing mode and per-app proxy settings: is your browser excluded, or are only selected apps being proxied? You can temporarily switch to global proxy mode for comparison, then restore your usual rules. Change one setting at a time and note its original value, or it will be difficult to pinpoint the cause.
If the logs repeatedly show domain name resolution failures, or some domains won’t load, check DNS. Start with the client’s default settings and make sure your phone’s date and time are set to update automatically. If you’ve manually configured Android “Private DNS,” temporarily switch it to Automatic and test again. Don’t treat “change DNS” as a universal fix for all connection problems.
4. What to check if only your browser won’t load pages
If other apps work normally, try accessing the same page in another browser and compare the results in a private window. Check the browser’s Secure DNS, proxy extensions, and cache. A private window doesn’t guarantee that all extensions are disabled. Don’t ignore certificate warnings or install root certificates from unknown sources.
If the problem persists, check the v2rayNG logs: timeouts point first to the network or node; authentication failures point to the configuration; and resolution failures point to DNS. These clues can only narrow down the cause. When asking for help, include your system and client versions, the error message, and the steps you’ve already tried. Don’t share your full subscription URL, UUID, or QR code containing credentials publicly.