What should you do if v2rayNG won’t connect? This guide walks you through low-risk checks to help determine whether the client hasn’t started, a node is unavailable, the subscription has a problem, or the current network is restricting access—and when it’s worth switching between Wi-Fi and mobile data. Start with checks you can easily undo; don’t rush to uninstall the app, clear its configuration, or reset your phone’s network settings.
1. First, determine whether the issue is with your internet connection or the proxy
- Stop v2rayNG and open a website you can normally access directly. If it still won’t load, check whether Wi-Fi requires you to sign in through a web page, whether your mobile data plan is active, and whether Airplane mode is on.
- Reopen the client, select a node, and tap Start. The first time you run it, allow the VPN connection request from Android. Without permission, a node can be listed but won’t be able to route your traffic.
- Temporarily stop other apps that use Android’s VPN connection, such as another VPN, an ad blocker with a local VPN mode, or a firewall, to prevent conflicts.
- Check your device’s date and time, and consider enabling automatic settings. A significantly incorrect time can cause certificate verification to fail.
A “Connected” status doesn’t mean the node is working—it may only mean that the phone’s local VPN service has started. Open a web page to verify that traffic is actually going through.
2. Check the node and subscription without repeatedly changing settings
First, make sure the selected node isn’t an outdated configuration. If you use a subscription, manually refresh it once through the subscription management or update menu, then select a node to test. Menu names may vary slightly between versions. A failed update doesn’t necessarily mean all your existing nodes are unavailable; the subscription address itself may simply be temporarily inaccessible.
If you imported a single link, check that you copied it in full, with no line breaks, truncation, or extra characters. Don’t guess at changes to the port, transport protocol, TLS, or server name; these settings must match the provider’s configuration. Try another node from the same subscription, or compare it with a configuration from a trusted source. The free nodes on this site can be used for a temporary test, but availability may vary.
Latency tests are only a guide: a failed test doesn’t always mean you can’t access web pages, and a reported latency doesn’t guarantee that traffic will work. Check actual access and the client logs as well.
3. When should you switch network connections?
If direct access works, VPN permission is enabled, and multiple nodes fail on your current network, it’s worth performing a one-time network comparison. Keep the same node and client settings, stop the connection, then switch from Wi-Fi to mobile data. Restart the connection and visit the same web page, keeping an eye on your data usage.
- Mobile data works but the original Wi-Fi doesn’t: the original network’s access policies, sign-in status, or connection may be the issue. You don’t need to reinstall the client right away.
- Neither network works, but other nodes do: the original node may be unavailable or its configuration may not match.
- No nodes work on either network: continue checking the subscription, client version, and logs. This alone isn’t enough to conclude that the network is restricted.
Use a network you trust for comparison; don’t connect to an unfamiliar hotspot just to test. Follow your school’s or employer’s network rules when using their network.
4. If it still fails, gather details before asking for help
Check the client logs for timeouts, DNS resolution failures, connection refusals, or certificate errors. A timeout may be related to the node or connection; a resolution failure calls for checking DNS and network status. If you see a certificate error, first check the time and configuration—don’t disable verification outright. If the connection only drops when the screen turns off, check background activity and battery restrictions.
When asking for help, include your Android and v2rayNG versions, the network you’re using, the error message, and the tests you’ve tried. Hide subscription links, UUIDs, and other credentials before sharing screenshots. Update the client through the project’s official release channels whenever possible, and back up your configuration first. Don’t make uninstalling and reinstalling your first step.