What should you do if v2rayNG won’t connect? This article walks you through troubleshooting in the following order: phone network → VPN permissions → node subscription → app settings. It covers issues such as tapping Connect and nothing happening, being connected but unable to open web pages, and node tests timing out. Change only one setting at a time and test again to avoid losing track of the cause after changing multiple settings at once.
1. Check your phone’s network and operating environment
- Disconnect v2rayNG and use your browser to open a website you can normally access. If that doesn’t work either, troubleshoot your Wi-Fi, mobile data, or account balance first. Public Wi-Fi may require you to complete a web-based sign-in.
- Switch between Wi-Fi and mobile data once. If you can connect on one network but not the other, the network itself may be restricting access; don’t rush to reinstall the client.
- Turn on your phone’s automatic date and time setting. An incorrect system time can cause TLS certificate verification to fail, preventing a connection to the node.
- Temporarily turn off other VPNs, accelerators, and ad blockers that use the local VPN service. Android generally cannot run two system VPN apps at the same time.
- Allow the system’s VPN authorization prompt when you start connecting. If no prompt appears, check your system VPN settings to see whether another app has “Always-on VPN” enabled or whether the option to block connections without a VPN is turned on.
2. Make sure the node was imported correctly and the subscription is still valid
Tap a node to select it before starting the connection. Having a configuration in the list doesn’t mean it’s the one currently in use. If you imported nodes through a subscription, check that the address is complete in subscription management, then update it. Menu names may vary slightly between versions.
A failed subscription update doesn’t mean all your existing nodes are invalid. Keep your current configuration and check whether the address is missing characters, contains spaces, or has expired. If the subscription address requires a proxy to access, use an existing working connection to update it, or ask the provider how to download it. Don’t repeatedly clear the list.
When importing VLESS, VMess, or other links individually, copy the entire link and avoid including any accompanying instructions. If you see a message that a transport type isn’t supported, update the client from the project’s official release page and check whether the node requires a newer core feature. When using free nodes from this site or other sources, also check when they were published and whether they’re still valid.
3. How to troubleshoot when it shows connected but web pages won’t open
The key icon only indicates that the local VPN is running; it doesn’t mean the remote node is working. Run the connection test provided by the client, then try visiting a website in your browser. A test timeout can offer a clue, but a single result isn’t enough to conclude that the node has failed.
- Try another node from a trusted source. If only one node fails, first check whether it’s no longer working or its parameters don’t match.
- Check your per-app proxy settings: your browser may be excluded from the proxy. Temporarily use settings that include the target app to test, then restore your usual rules.
- Temporarily switch routing modes to check whether the rules are causing the issue—for example, test with global proxy mode. Once you’ve identified the cause, restore the original mode.
- If the logs report a domain name resolution failure, check whether you manually changed your DNS settings or enabled a custom Private DNS. Note the original value and restore the default settings to test. Don’t blindly copy DNS addresses from unknown sources.
4. Use the logs to pinpoint the issue and avoid making a mess of your settings
Check the logs after a connection fails: “timeout” commonly indicates a broken connection or an unreachable node; “connection refused” may mean the remote port isn’t accepting connections; and a certificate error calls for checking the time and node domain parameters. These messages aren’t conclusive on their own, so consider the results of switching networks and nodes as well.
Don’t disable certificate verification just to get rid of an error, and don’t install modified APKs from unknown sources. When asking for help, include the client version, network type, a snippet of the error, and the steps you’ve tried. Hide credentials such as your subscription address and UUID; there’s no need to share the full node link.