What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: your phone’s network, VPN permissions, node subscriptions, routing, and logs. It covers issues such as tapping Start but still being unable to access the internet, node tests timing out, or certain apps not opening. You don’t need to reinstall your phone or change the server configuration. First, identify which layer is causing the problem.
1. Check your phone’s network and VPN setup
Before troubleshooting, stop v2rayNG and make sure your phone can access the internet on its own. A VPN icon in the status bar only means the local VPN has started; it doesn’t mean the node is working.
- Open a website you can normally access directly. If it won’t load either, first check for Wi-Fi sign-in requirements, a weak mobile signal, or an unpaid bill.
- Switch between Wi-Fi and mobile data once. If the connection fails on only one network, the cause may be restrictions or an authentication issue on that network.
- Turn off other VPNs, accelerators, and ad blockers that use a local VPN to avoid conflicts over Android’s VPN connection.
- Allow the system’s VPN connection request the first time you start the app. If “Always-on VPN” or “Block connections without VPN” is enabled, check whether either setting is preventing internet access during troubleshooting.
- Enable automatic date, time, and time zone settings. A significantly incorrect clock can cause TLS certificate verification to fail.
2. Check that the node was imported correctly and the subscription hasn’t expired
In the configuration list, make sure the node you want to use is selected before starting the connection. When importing a link, copy the entire link without adding explanatory text, spaces, or line breaks. A blurry QR code may also fail to scan correctly.
If you use a subscription, check its URL in subscription management and then update it. A successful subscription update doesn’t mean every node in it is reachable. Free nodes may be down or temporarily unavailable, so try another node for comparison. Free nodes provided on this site should also be judged by their actual connection results.
If the subscription won’t update, first check that the URL is still valid and that no access token is missing. Don’t repeatedly delete all your configurations. Keep the original configuration and import another copy to compare. For settings such as UUID, password, and transport protocol, follow the information provided with the node rather than guessing.
3. If connected but webpages won’t load, check routing and DNS
If the service starts normally but only certain websites or apps are inaccessible, first check whether per-app proxying is enabled and whether the affected app is excluded. Also check whether the mode is set to “Proxy only selected apps” or “Bypass selected apps”—these settings have opposite effects.
You can temporarily switch to global proxy mode for comparison, then restore your usual routing mode after testing. Global mode helps narrow down the issue; it can’t fix a node that’s no longer working. If global mode works but your usual mode doesn’t, focus on the routing rules and per-app settings.
If only domain names are affected, check the DNS settings in v2rayNG and Android’s Private DNS. If you previously changed these settings manually, note the original values, restore the defaults, and test each setting one at a time. Avoid changing multiple options at once, or it will be difficult to identify the cause.
4. Use the logs to decide what to check next
Open the logs in the app, clear the old entries, reconnect, and try to visit a webpage. A timeout usually means the connection timed out; “connection refused” means the connection was rejected. Certificate or TLS errors call for checking the date and time, client version, and node settings, but none of these messages alone can pinpoint the root cause.
Finally, check for updates through the project’s official release channels and avoid modified versions from unknown sources. When asking for help, provide the client version, Android version, network type, and redacted logs. Don’t share your full subscription URL, UUID, or password. Changing one thing at a time in order is more likely to help you find the problem than reinstalling repeatedly.