What should you do if v2rayNG won’t connect? This guide helps you distinguish between local network issues, unavailable nodes, subscription import errors, and phone permission restrictions. If you can’t open webpages after connecting, tests time out, or the connection keeps dropping, follow the checks below in order. Change only one thing at a time to avoid making the problem harder to diagnose.
1. First, make sure your phone can connect to the internet
Close v2rayNG first, then check your basic network connection. Try opening a website you can usually access directly. If it won’t open either, troubleshoot Wi-Fi, mobile data, or network sign-in issues before repeatedly switching nodes.
- Turn off the proxy, then test your connection in a browser and another app to make sure the issue isn’t limited to one website.
- Switch between Wi-Fi and mobile data, then test the same node again. If it fails on only one type of network, the issue may be related to that network environment.
- On public Wi-Fi, complete the web sign-in process first. Also check Airplane mode, your data balance, and the app’s network permissions.
- Set your system date, time, and time zone to automatic. A significantly incorrect time can cause TLS certificate verification to fail.
If mobile data works but your current Wi-Fi doesn’t, try reconnecting to Wi-Fi or restarting your router. Don’t reset your phone’s network settings after just one failure; doing so will erase some saved settings.
2. Check that the node and subscription are valid
Return to v2rayNG, make sure the configuration you want to use is selected, and then connect. A successful subscription update only means the configuration was retrieved; it doesn’t mean that every node in it is available. Free nodes can also expire or become temporarily unreachable, so free nodes provided by this site need to be tested as well.
- Update the subscription manually and check for any error messages. If the update fails, make sure the subscription URL is complete and hasn’t expired. Don’t share links that contain tokens.
- Use the connection test feature provided by the client, then try opening a webpage. Test names vary by version, and a latency result on its own doesn’t confirm that you can actually access websites.
- Switch to another node from a trusted source. If only one node fails, the node itself is the most likely cause. If all nodes fail, check your phone and client instead.
- If you imported the configuration using a QR code or clipboard, make sure the content wasn’t truncated. Verify each manually entered setting with the provider. Don’t guess at changes to the port, UUID, transport method, or TLS settings.
3. Rule out VPN conflicts and routing issues
When connecting, allow Android’s VPN connection request. Check whether another VPN, firewall, or ad-blocking tool that uses a local VPN is active on your system. Close those apps and try again to avoid conflicts over the VPN connection.
If the client shows as connected but only some apps won’t open, check whether those apps are excluded from v2rayNG’s per-app proxy settings, or whether routing rules are sending their traffic directly. You can temporarily switch to a routing mode that proxies all traffic for comparison, then restore the appropriate setting after testing. The exact names vary by version.
If the connection drops only after the screen is locked, allow v2rayNG to run in the background and check battery optimization and power-saving restrictions. If you need to update the client, get the installation package from the project’s official release channel. Avoid modified versions from unknown sources.
4. Use the logs to narrow down the issue
Keeping the error details is more useful than changing settings at random. After a connection fails, check the logs. A timeout usually means the destination didn’t respond in time; a connection refusal may be related to the destination service’s status; and a certificate error means you should check the time, configuration, and client version—not simply assume the connection is slow.
If the logs show a domain name resolution error, first check whether Android’s “Private DNS” is set to a custom service that isn’t available. You can temporarily switch it to automatic and test again. Don’t bypass the error by disabling certificate verification.
If the issue persists, note the client version, network type, scope of the failure, and key error messages. Before asking for help, redact your subscription URL, UUID, and other credentials so others can diagnose the problem without exposing access to your nodes.