What should you do if v2rayNG won’t connect? This guide troubleshoots the issue in order: your device’s network, VPN permissions, node subscriptions, and proxy mode. It helps you distinguish between the app failing to start, connection timeouts, and being connected but unable to open webpages. Don’t reinstall repeatedly or change node settings at random. Adjust one thing at a time so you can identify the cause.
1. Check your phone’s network before connecting
First, make sure your network works without a proxy. Turn off v2rayNG and use your browser to visit a site that normally works without a proxy. If it still won’t load, troubleshoot your Wi-Fi, mobile data, or account balance before switching nodes.
- Public Wi-Fi may require you to sign in through a web page. Pause the proxy and complete the login for the hotel, campus, or shopping center network before trying to connect.
- Switch between Wi-Fi and mobile data to test. If only one network fails, the problem may be due to that network’s restrictions or a DNS issue.
- Set your system date, time, and time zone to automatic. An incorrect time can cause TLS certificate validation to fail.
- Pause other VPNs, accelerators, and ad-blocking tools that use a local VPN to avoid competing for Android’s VPN connection.
If you’ve configured Private DNS on your phone and get DNS resolution errors after connecting, temporarily set it to “Automatic” and test again. Restore your preferred setting afterward; there’s no need to leave it disabled.
2. Confirm that v2rayNG has started successfully
After selecting a node, tap Start. The first time you run the app, you’ll need to approve Android’s VPN connection request. If you accidentally tapped Cancel, start the app again and grant permission. The VPN icon in the notification bar only means the local tunnel has been established; it does not mean the remote node is necessarily working.
If the connection drops as soon as you switch to another app, allow v2rayNG to run in the background in your system app settings and consider relaxing battery restrictions. Menu names vary by phone, so focus on battery-saving policies and background network permissions. Get the client from the project’s official release channel to avoid modified versions from unknown sources.
3. Check whether your subscription and nodes are valid
- Update your subscription manually and check for a download error. If the update fails, make sure the subscription link is complete and hasn’t expired. Don’t post the link publicly in a group.
- Make sure you’ve selected the node you want to use—not just imported it. Then test a node from a different source or route so you’re not relying on a single failed node.
- Use the client’s connection test or try visiting a website to help identify the problem. A single latency result doesn’t guarantee that webpages will load, so test by opening a page too.
- If the node came from an old share, get a current working configuration. The free nodes on this site can be used for a temporary comparison, but availability may change and they are not guaranteed to stay online.
For configurations such as VLESS and VMess, the address, port, transport method, and TLS-related settings must match. Don’t guess at port or SNI changes, or disable certificate verification; instead, re-import the complete link provided by the service.
4. What if it says connected but webpages won’t open?
First, check the routing mode and per-app proxy settings. If your browser is excluded, it won’t use the proxy. Temporarily switch to global proxy mode to test. If global mode works but rule mode doesn’t, check your rules and app routing first, then restore your usual mode after testing.
Next, look for key errors in the logs: “timeout” usually means the connection timed out, so check both the network and the node; a certificate error calls for checking the time and configuration; and a resolution failure points to DNS. Before sharing logs to ask for help, hide server addresses, UUIDs, subscription links, and other sensitive information.
Retest in this order: “direct connection works → permission granted → subscription updated → node changed → routing checked.” If other nodes work, the problem is likely with the original node. If all nodes fail, check the client’s permissions and network environment again.