What should you do if v2rayNG won’t connect? This guide troubleshoots the issue in order: local network, Android permissions, node subscription, routing, and logs. It covers problems such as losing internet access after startup, node timeouts, or certain apps failing to load. Change only one setting at a time, then reconnect and test so you can identify the cause instead of having several changes muddy the results.
1. First, make sure your phone can access the internet
- Close v2rayNG and use a browser to visit a website that normally works. If it still won’t load, troubleshoot your Wi-Fi or mobile data first rather than rushing to switch nodes.
- Switch between Wi-Fi and mobile data to test both. Public Wi-Fi may require you to complete authentication in a browser first. If mobile data isn’t working, check your data balance and the app’s network permissions.
- Temporarily turn off other VPNs, accelerators, or blocking tools that use the local VPN mode. Android usually can’t run multiple services of this kind at the same time.
- Set your phone’s date and time to automatic. A significant discrepancy in the system time can cause certificate verification to fail.
If v2rayNG only fails to connect on a particular Wi-Fi network but works on mobile data, check that network’s authentication requirements, access restrictions, and router status first. Don’t assume the client is broken.
2. Check that v2rayNG has actually started
Select a node and tap the Start button on the main screen. When starting the app for the first time, allow the VPN connection request that appears. If you accidentally tapped Cancel, start the app again and grant permission. Check whether the VPN icon appears in the Android status bar, and make sure the app doesn’t stop immediately or display an error.
In your system app settings, allow v2rayNG to use the network as needed. If the connection often drops after the screen locks, allow background activity and set the battery policy to Unrestricted. Menu names may vary by phone. The VPN icon only means the local service has started; it doesn’t mean the remote node is available.
3. Update your subscription and verify the node details
- If your nodes come from a subscription, check that the address is complete in the subscription settings, then update it. If the update fails, first check whether the subscription link is accessible on your current network. Don’t post the link in a public group chat.
- Select an updated node and run the connection test provided by the client. A timeout only means that the test didn’t succeed; check whether you can access websites in your browser to help determine the cause.
- Test against another node from a trusted source that uses a supported protocol. Free nodes may expire or become temporarily unavailable; free nodes provided by this site should also be judged by their actual test results.
- If importing manually, check the address, port, user ID, and parameters such as TLS and transport. Whenever possible, reimport the original link rather than changing settings by guesswork.
4. Connected but can’t access websites? Check routing and logs
If only some apps can’t access the internet, check whether per-app proxying is enabled and whether the affected apps are excluded. Temporarily switch to the client’s global proxy route for comparison. If access is restored, review the existing routing rules. Restore your usual mode after testing.
If you see a domain resolution error, first restore any DNS settings you changed yourself, or Android’s Private DNS setting, to Automatic, then reconnect and test. Don’t change multiple DNS settings at once. Check the logs for messages such as timeouts, connection refusals, or certificate verification failures. These point to areas to investigate—such as the network path or node, the remote port, the system time, or TLS parameters—but don’t by themselves confirm a specific cause.
When asking for help, provide the client version, network type, and sanitized logs, and hide credentials such as subscription links and user IDs. If the problem persists after switching networks and trying a trusted node, check for updates through the project’s official release channels, and avoid installing modified versions from unknown sources.