What should you do if v2rayNG won’t connect? This guide troubleshoots the issue in this order: your device’s network, VPN permissions, node configuration, DNS, and logs. It will help you distinguish between a network outage, an invalid configuration, and an app conflict. Change one setting at a time and test immediately afterward, so you can identify the cause instead of losing track after changing several settings at once.
1. First, make sure your phone can access the internet
- Stop v2rayNG and open a browser to visit a website you can normally access directly. If that doesn’t work either, troubleshoot your Wi-Fi or mobile data first; don’t rush to change your node.
- On public Wi-Fi, complete the sign-in process in your browser first. Then test with mobile data, keeping an eye on your data usage.
- Temporarily turn off other VPNs, accelerators, firewalls, and ad blockers that use Android’s local VPN mode. Android typically does not allow multiple apps of this kind to establish VPN connections at the same time.
- Set your system date, time, and time zone to automatic. An incorrect time can cause TLS certificate validation to fail.
If the same node fails on Wi-Fi but works on mobile data, first check for restrictions or DNS issues on the current network. However, a single test isn’t enough to confirm the cause.
2. Check VPN permissions and background restrictions
Open v2rayNG, select the configuration you want to use, and tap the start button. The first time you connect, you’ll need to allow the VPN connection request shown by the system. If no prompt appears or the connection stops immediately, go to the VPN section in your system settings and check whether another app has enabled “Always-on VPN” or “Block connections without VPN.” The exact menu names vary slightly between phones.
If the connection works while the screen is on but drops when the screen locks, allow v2rayNG to run in the background and set its battery usage to unrestricted. The VPN icon in the status bar only means the tunnel has been established; it doesn’t guarantee that the node is working, so open a webpage to verify the connection.
3. Make sure the node and subscription are still valid
- Check that you’ve selected the configuration you intend to use, rather than an old node that remained selected after importing a new one.
- If you use a subscription, update it and check whether the configuration was retrieved successfully. If the update fails, stop the proxy and try again on a network that allows direct access. If it still fails, contact your provider to confirm that the subscription URL is valid.
- When importing a link manually, make sure you copied it in full without extra spaces or truncation. It’s best to reimport the original link rather than guess at changes to the port, UUID, transport method, or TLS settings.
- Test another node from a trusted source that has been updated recently. The free nodes on this site can also help with troubleshooting, but their availability may change, so don’t use them to judge whether every network is working.
Latency test results are only a guide: a timeout may be related to the test target or method, and a displayed latency value doesn’t guarantee that webpages will load properly.
4. Use DNS, routing, and logs to pinpoint the issue
If some websites won’t open after connecting, check that the routing mode hasn’t been set to direct connection by mistake. You can temporarily switch to the global proxy mode provided by the client for comparison, then switch back after testing. If you’ve manually configured Android’s “Private DNS,” note the original value and try setting it to Automatic. Avoid repeatedly changing the client’s custom DNS settings as well.
Open the v2rayNG logs and find the error from your most recent connection attempt. “timeout” usually indicates a connection timeout, “certificate” is often related to certificate validation, and “lookup” or DNS messages are reasons to check name resolution first; the exact meaning still depends on the surrounding log context. When asking for help, provide the client version, network type, and relevant error excerpt. Be sure to hide your subscription link, UUID, password, and other credentials.