What should you do if v2rayNG won’t connect? This guide troubleshoots issues in the order of local network, system permissions, node subscriptions, routing, and DNS. It helps you tell the difference between the app failing to start, a node timing out, and webpages not loading after connecting. Don’t repeatedly uninstall the app or change settings at random. Change just one setting at a time and test so you can pinpoint the cause.
1. Turn off the proxy and confirm your phone can access the internet
- Disconnect v2rayNG and use your browser to visit a domestic website that normally works. If it won’t load either, troubleshoot your Wi-Fi, mobile data, or broadband connection first.
- Public Wi-Fi may require you to sign in through a webpage. Complete the sign-in before starting the proxy, and don’t ignore any system prompt to “Sign in to network.”
- Test the same node over both Wi-Fi and mobile data. If it fails on only one network, the issue may be related to that network’s access restrictions or routing—not necessarily a faulty client.
- Temporarily disable other VPNs, accelerators, and filtering tools that use Android’s local VPN mode. Android generally can’t run multiple VPN services at the same time.
First make sure you can access the internet without a proxy before continuing; otherwise, your node test results may be affected too.
2. Check VPN permissions and background restrictions
Select a node in v2rayNG and tap Start. The first time you connect, allow the system to create a VPN connection. If you tapped Deny by mistake, try starting again and grant permission. Button names may vary slightly by version.
If the connection drops as soon as you lock your screen, open your phone’s settings for v2rayNG, allow background activity, and adjust battery optimization and background data restrictions as needed. If the system has “Always-on VPN” or “Block connections without VPN” enabled, make sure they aren’t set to use another app; otherwise, your entire phone may lose internet access when the proxy stops.
3. Check that your node and subscription are valid
- Make sure you’ve selected the node you want to use, not just imported it. Run a connection test, then try opening a webpage. A latency result alone doesn’t confirm that you can access websites.
- Refresh the list using the client’s subscription update feature, and check for any update errors. A failed update doesn’t necessarily mean your existing nodes are invalid, but the list may be out of date.
- Try another node from a trusted source for comparison. Free nodes may be temporarily unavailable, and nodes shared on this site should also be judged by their actual connection status at the time.
- If you see a configuration error after importing, copy the full link again or scan the original QR code. Don’t guess at changes to the port, transport, TLS, or server name.
If all nodes time out on the same network, check the network and client first. If only certain nodes fail, the issue is more likely with those nodes or their routes.
4. What to check if the app connects but webpages won’t load
First, check the routing mode. With split-routing modes such as bypassing domestic addresses, domestic websites normally connect directly. Temporarily switch to global proxy mode to compare, then restore your previous setting after testing. If per-app proxying is enabled, make sure your browser hasn’t been excluded.
If the logs show a domain name resolution error, check whether Android’s “Private DNS” is set to a service that can’t be reached. Switch it back to Automatic and test again. Don’t change multiple DNS settings at once. Also set your system date and time to automatic—a significantly incorrect clock can cause TLS verification to fail.
5. Check the logs and provide details when asking for help
Open the client logs and try connecting again. A timeout usually means the connection timed out; a resolution error calls for checking DNS; a certificate error means you should check the time and node configuration. Don’t hide the problem by disabling certificate verification. If the issue persists, note the client version, network type, exact error message, and results after switching networks. Before sharing screenshots, hide sensitive information such as subscription URLs and UUIDs to avoid exposing your node credentials.