What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: your local network, VPN permissions, node subscriptions, routing, and logs. It covers issues such as websites not loading after startup, node timeouts, and some apps being unable to connect. There’s no need to keep reinstalling the app—first determine whether the client failed to start or started but isn’t routing traffic.
1. Check your network and VPN environment
Disconnect v2rayNG and use your browser to visit a website that normally works without it. If that site won’t load either, troubleshoot your Wi-Fi, mobile data, or public network sign-in first. Don’t rush to change node settings.
- Switch between Wi-Fi and mobile data, and test each one. If only one network fails, the issue may be related to that network’s restrictions or connection status.
- Turn off other VPNs, accelerators, and filtering tools that use Android’s local VPN mode. Android usually can’t run multiple connections of this type at the same time.
- Tap the connect button in v2rayNG and confirm the VPN permission prompt from the system. If you’re told that another VPN is already active, check your system VPN settings.
- Set your phone’s date and time to automatic. A significant time error can cause TLS certificate verification to fail.
- If the connection drops when the screen locks, allow the app to run in the background in system settings and relax battery restrictions as needed.
The VPN icon only indicates that a tunnel has been established; it doesn’t guarantee that the node is working. You’ll also need to test whether you can actually access websites.
2. Make sure your node and subscription are valid
Open the configuration list and make sure the node you want to use is selected. Importing a node doesn’t automatically switch to it. If you use a subscription, update it first, then check for errors or an empty list.
- Subscription update fails: Check that the link is complete and contains no extra spaces, and see whether the provider says it has expired. A failed update doesn’t necessarily mean all existing nodes are unavailable.
- Manual import fails: Make sure you copied the complete share link, not a webpage URL or truncated text.
- A single node times out: Try other nodes in the same subscription, then try nodes from a different source to distinguish an individual node failure from a local issue.
- All nodes fail: First recheck your network, client version, and import compatibility. Don’t change ports or transport settings at random.
Free nodes may become unavailable temporarily. Free nodes provided by this site should also be verified through testing. Latency test results can help you assess a node, but whether you can actually access websites is what matters.
3. If connected but websites won’t load, check routing and DNS
Disconnect and reconnect, then use your browser to open two different websites. If only certain apps fail, check whether per-app proxying is enabled and whether those apps have been excluded.
You can temporarily switch to the global proxy routing mode provided by the client for testing. The mode’s name may vary by version, and it is not the same as Android’s VPN mode. If switching modes fixes the issue, focus on your existing routing rules. When you’re done testing, switch back to the mode that suits your everyday use.
If the logs repeatedly show domain resolution failures, check your DNS settings. First restore the client’s default settings, then check whether Android’s “Private DNS” is set to an unreachable service. If needed, temporarily set it to automatic and test again. Change only one setting at a time, and note its original value.
4. Check the logs instead of reinstalling unnecessarily
Clear the old logs, reconnect, try opening a webpage, and then check the latest errors. A timeout usually means the connection didn’t complete in time. Certificate-related errors call for checking the time, client version, and node settings; resolution errors point to DNS. A single error message does not, by itself, prove the cause of the problem.
If the issue persists, note your Android and v2rayNG versions, network type, which apps or sites are affected, and any key errors, then contact your node provider. Before sharing screenshots, hide sensitive information such as subscription links, UUIDs, and passwords. Download client updates from the project’s official release channels and avoid modified versions from unknown sources.