What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: your network, node subscriptions, phone permissions, and connection logs. It will help you determine whether the issue is with your network, an inactive node, or the client settings. It applies to Android phones experiencing connection timeouts, no internet access after connecting, or problems opening certain apps.
1. First, make sure your phone can access the internet
Don’t start by changing advanced settings. Disconnect v2rayNG and try opening a website you normally visit directly. Confirm that Wi-Fi or mobile data is working. If you still can’t access the internet with the proxy turned off, first check your phone’s network connection, data plan, or Wi-Fi sign-in requirements.
- Disconnect v2rayNG and check whether your browser can open a regular webpage. If you’re using public Wi-Fi, complete the sign-in process first.
- Switch between Wi-Fi and mobile data, then connect using the same node to see whether the results differ.
- Temporarily quit any other VPNs, accelerators, or filtering tools that use Android’s local VPN mode, as they may conflict over the VPN connection.
- Set your phone’s date, time, and time zone to automatic. An incorrect time can cause TLS certificate verification to fail.
Change just one thing at a time, then test again so you can identify what worked. If mobile data connects but a particular Wi-Fi network doesn’t, the issue is more likely related to that network’s restrictions or DNS resolution. You don’t need to reinstall the client right away.
2. Check that the node is working and the subscription is up to date
Open v2rayNG and make sure you’ve selected the node you want to use; importing it alone isn’t enough. For nodes added through a subscription, use the relevant menu to update it. Menu names may vary slightly between versions. If the update fails, first check that the subscription URL is complete and hasn’t expired. Don’t change its parameters arbitrarily.
Copy the node link again from a trusted source, making sure you haven’t missed the protocol name at the beginning or any parameters at the end. If you’re using free nodes from sources such as this site, check the publication date and any validity notices. Free nodes can stop working or become congested, so a successful import doesn’t mean a node is currently usable.
A latency test returning a value doesn’t guarantee that webpages will open. Use the client’s real connection test if available, then try opening the target webpage to verify. You can also test another node from a trusted source to see whether the problem is limited to a single node.
3. Check VPN permissions and proxy mode
The first time you start the app, Android will ask for permission to create a VPN connection. If you accidentally denied it, stop and restart the app, then approve the request. If the connection switches off immediately after you turn it on, check whether another VPN is running and whether the system is restricting v2rayNG’s background activity.
While troubleshooting, you can temporarily select the client’s global proxy mode and make sure your browser isn’t excluded from the proxy by per-app settings. If global mode works but rule-based mode doesn’t, check your routing rules and app list. When you’re done testing, switch back to the mode that suits your everyday use so unrelated traffic doesn’t go through the proxy.
4. Use the logs to narrow down the problem
Clear the old logs, reconnect, reproduce the webpage issue once, and check the latest error. A timeout only indicates that a connection timed out; it doesn’t, by itself, prove that the node has been blocked. An offline node, network restrictions, or a problem with the route can all cause timeouts. If you see messages mentioning certificate or TLS, first check your system time and node details. If you see messages mentioning resolve or DNS, focus on domain name resolution rather than blindly copying unfamiliar DNS settings.
If the problem persists, note the client version, Android version, network type, whether all nodes fail, and the error message with sensitive details removed. Before sharing a screenshot, make sure to hide your subscription URL, UUID, password, and other sensitive information. Update the client through the project’s official release channels first. Back up your configuration before considering a reinstall to avoid losing subscriptions that may still work.