What should you do if v2rayNG won’t connect? This guide walks through troubleshooting in the order of “local network, VPN permissions, node subscription, routing, and DNS” to help you tell whether the problem is your phone’s internet connection, an invalid configuration, or an app setting. It is intended for Android users and requires no server-side changes. Menu names may vary slightly between versions.
1. First, make sure your phone can access the internet
Disconnect v2rayNG, then try opening a few websites you use regularly. If they still won’t load, troubleshoot your Wi-Fi, mobile data, or campus network login first instead of repeatedly switching nodes.
- With the proxy off, try two different websites to make sure the issue isn’t with just one site.
- Switch between Wi-Fi and mobile data, then test again. If public Wi-Fi requires a web login, complete that login first.
- Temporarily disable any other VPNs, accelerators, or ad blockers that use a local VPN. Android usually can’t run multiple VPN services at the same time.
- Set your system date and time to automatic. A significantly incorrect time can cause TLS certificate validation to fail.
Change only one thing at a time and keep track of the results. If the same node works on mobile data but fails on Wi-Fi, focus on that Wi-Fi network’s login, restrictions, or DNS rather than assuming the node is down.
2. Check VPN permissions and node configuration
Return to v2rayNG, select the node you want to use, and tap the start button. The first time you connect, select Allow when Android prompts you to authorize the VPN connection. If it doesn’t start normally, check whether another app is using the VPN in your system settings, or whether “Always-on VPN” is assigned to another app.
- For subscription users: Open the subscription settings and make sure the subscription URL is complete, then update it. If the update fails, check whether your local connection is down or the subscription has expired.
- For users importing a link: Copy the full vmess:// or vless:// link again, making sure it hasn’t been truncated, wrapped onto multiple lines, or had characters omitted by your messaging app.
- Check that the address, port, transport, TLS, and other configuration fields match the provider’s settings. Don’t disable certificate verification without a good reason.
A successful subscription update doesn’t mean the node is working. Try another node for comparison; free nodes may have expired or be temporarily unreachable. If you’re using a free node from this site, follow the instructions on its page and don’t mix parameters from different configurations.
3. If the connection starts but webpages won’t load, check routing and DNS
The VPN icon in the status bar only means that the local VPN has started; it doesn’t confirm that the remote connection is working. Run the client’s connection test, then verify by opening an actual webpage. A timeout is a clue, but on its own it doesn’t prove that the node is down.
If only some apps can’t connect, check whether per-app proxying is enabled and whether the affected app has been excluded. You can also temporarily switch to global proxy mode to test, then restore your original routing mode so unrelated traffic doesn’t go through the proxy.
If the logs repeatedly report DNS resolution failures, check whether Android’s “Private DNS” is set to a custom address that can’t be reached. Temporarily switch it to Automatic and try again. Don’t change nodes and multiple DNS settings at the same time, or it will be difficult to identify the cause.
4. Use the logs to investigate further
Open the log page, reconnect once, and look for the latest error. A timeout often indicates an unreachable destination or a restricted connection; “connection refused” may mean there’s no service listening on the target port; a certificate error calls for checking your device’s time and the server name in the configuration. Log messages point you in a direction; they aren’t a definitive diagnosis.
If it still doesn’t work, note the client version, network type, whether all nodes fail, and any key error messages, then contact the configuration provider for help. Before sharing screenshots, hide your subscription link, UUID, and other sensitive information. Don’t share your full configuration publicly.