What should I do if v2rayNG won’t connect? This article troubleshoots issues in the order of “local network, VPN permissions, node subscription, routing, and logs” to resolve problems such as tapping Connect with no response, being connected but unable to open webpages, or node tests timing out. There’s no need to keep reinstalling the app, and you shouldn’t start by changing parameters you don’t understand.
1. Check your phone’s network and operating environment first
- Disconnect v2rayNG and use your browser to visit a domestic website that normally works. If it won’t load either, first check your Wi-Fi or mobile data, or whether your account has run out of credit. Public Wi-Fi may require you to complete web-based authentication first.
- Switch between Wi-Fi and mobile data to test. If the same node fails on only one network, the cause may be that network’s restrictions or connectivity—not necessarily a client issue.
- Turn off other VPNs, accelerators, and ad blockers that use Android’s local VPN mode. Android usually cannot run two such VPN services at the same time.
- Set your system date, time, and time zone to automatic. An incorrect time can affect TLS certificate verification and cause handshakes with some nodes to fail.
Change only one setting at a time. After each change, disconnect and reconnect, then test the same webpage so you can tell which step helped.
2. Confirm that the client has actually established a connection
When you tap Connect for the first time, allow the Android VPN connection request that appears. If no prompt appears or startup fails, check your system’s VPN settings to see whether another app is occupying the VPN slot and whether restrictions such as “Always-on VPN” are assigned to another app. Menu names may vary by phone.
If the connection drops immediately or stops working when the screen is locked, allow v2rayNG to run in the background and check your battery optimization and data usage restrictions. Get the client’s stable release from the project’s official distribution channels. Don’t install modified versions from unknown sources or trust additional root certificates without a good reason.
3. Check whether the node and subscription are valid
- Make sure the node you want to use is selected on the main screen; importing it and leaving it in the list is not enough. A node appearing by name does not mean its configuration is complete or the service is available.
- Open subscription management and manually update the subscription. Check for errors. If the update fails, make sure the link was copied in full and contains no extra spaces, and check whether the subscription has expired or requires you to renew it on the provider’s website.
- Select a node and use the client’s connection test feature. Menu names may vary between versions. Treat the latency result as a guide; actual webpage access is what matters.
- Try another node from a trusted source that has been updated recently. You can also use this site’s free nodes for comparison, but availability may change and continuous service is not guaranteed.
Don’t guess at changes to the port, UUID, transport, or TLS settings. If the configuration is incomplete, re-import the full link or QR code provided by the provider. Subscription URLs may contain access credentials, so don’t share them publicly.
4. Connected, but webpages still won’t open
First check the routing mode and temporarily switch to global proxy mode to test. If global mode works but split tunneling doesn’t, focus on the routing rules and which apps are included in the proxy. Make sure your browser isn’t excluded from the proxy, then switch back to the mode that suits your everyday use after testing.
If you see a domain resolution error, check whether you’ve manually set an unreachable DNS server and try restoring the client’s default settings. If custom Private DNS is enabled on your system, you can also temporarily change it and test again. Don’t change multiple settings at once.
Finally, check the logs: a timeout usually points to a network issue or an unreachable node; for a certificate error, check the system time, node domain, and configuration completeness; for an authentication failure, verify the node credentials. When asking for help, include the exact error message, client version, and network type, but redact subscription links, UUIDs, passwords, and other sensitive information so the issue can be diagnosed safely and efficiently.