What should you do if v2rayNG won’t connect? This guide helps you distinguish between a local network outage, a VPN permission conflict, an unavailable node, and a DNS issue, then troubleshoot connection problems on your Android phone in order. It applies if you can’t access the internet after tapping Start, a node times out, or the app shows Connected but webpages won’t load.
1. First, make sure your phone can access the internet
Stop v2rayNG before testing your basic network connection; don’t start by changing node settings. If your basic connection isn’t working, switching subscriptions won’t fix the problem.
- Stop v2rayNG, then try opening a website or app that normally works without a proxy to see if it loads.
- If you’re using public Wi-Fi, complete any sign-in on the captive portal. If you see a “Sign in to network” prompt, open it and follow the instructions.
- Test Wi-Fi and mobile data separately. If only one fails, check that network’s sign-in status, signal strength, and access restrictions first.
- Temporarily turn off other VPNs, ad blockers with VPN features, and network-accelerator apps to prevent them from competing for Android’s VPN connection.
If you still can’t access the internet with the client stopped, try toggling Airplane mode, reconnecting to Wi-Fi, restarting your router if necessary, or contacting your network provider.
2. Check VPN permissions and node import status
Open v2rayNG, select the node you want to use, then tap the Start button. When Android asks for permission to set up a VPN connection for the first time, allow it. Importing a node alone does not mean you’re connected.
- Check that a node is selected, and look at the status at the bottom of the app and the VPN icon in the system status bar.
- If you imported nodes from a subscription, update the subscription first. If the update fails, check that the link is complete and hasn’t expired; don’t repeatedly paste it over the existing one.
- When importing a link manually, make sure the protocol identifier at the beginning is intact and that the link doesn’t contain extra spaces, line breaks, or explanatory text.
- Set your phone’s date and time to automatic. An incorrect time can cause TLS certificate verification to fail.
Don’t change the port, transport method, or TLS settings at random; they must match the node’s actual configuration. Reimporting from a trusted source is usually more reliable than guessing the settings.
3. Narrow down the cause by switching nodes and networks
Use the connection test feature in the client; its name may vary by version. A single timeout is only a clue: an unreachable test target can also affect the result, so check whether webpages load as well.
- Try a different node on the same network. If only certain nodes fail, the node may be unavailable or its configuration may not match.
- Test the same node on both Wi-Fi and mobile data. If it fails on only one network, the problem is more likely related to that network.
- If all nodes fail, check the subscription source, VPN permissions, and client version. There’s no need to keep rerunning speed tests.
Free nodes provided by this site may also become unavailable due to maintenance or usage changes. Use the actual connection results as your guide.
4. What to do when you’re connected but webpages won’t open
First, check whether the problem affects only certain apps. Review v2rayNG’s per-app proxy settings; the affected app may be excluded. Then check the routing mode to confirm that traffic to the destination is being proxied. You can temporarily switch to global proxy mode for comparison, then restore your original settings after testing.
If the logs report a domain resolution failure, check your DNS settings. If you’ve set a custom DNS or enabled Android’s “Private DNS,” note the original value, then temporarily restore the default or automatic setting and test again. Avoid changing multiple settings at once. A timeout doesn’t necessarily mean there’s a DNS problem, so don’t change DNS just because a webpage won’t open.
If the issue persists, check the project’s official release channels for a client update, and note the version, network type, and error logs. Before asking for help, be sure to hide subscription links, UUIDs, passwords, and other sensitive information. If you see a certificate error, don’t disable certificate verification to force a connection.