What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: phone network, VPN permissions, node subscriptions, routing and DNS, then logs. It covers issues such as startup failures, being connected but unable to open web pages, and some apps being unable to access the internet. Change and test only one setting at a time so you can identify the cause.
1. Check your phone’s network and VPN environment
- Stop v2rayNG and try opening a website that normally works without a proxy. If it still won’t open, switch between Wi-Fi and mobile data to confirm that your basic connection is working. Public Wi-Fi may also require you to complete a sign-in page first.
- Turn off any other VPNs, accelerators, or ad-blocking tools that use the VPN connection. Android usually allows only one VPN service to run at a time, so multiple tools may conflict.
- Start v2rayNG and allow the VPN connection request when prompted by the system. If the request is blocked, check your system’s VPN settings for another app that has enabled “Always-on VPN” or “Block connections without VPN.”
- Set the system date and time to update automatically. A significant time discrepancy can cause certificate verification to fail. Don’t bypass the issue by disabling certificate verification.
First make sure your network is working, then check whether the node is unavailable. If the connection fails only on a particular Wi-Fi network but works on mobile data, investigate restrictions on that network instead of repeatedly reinstalling the client.
2. Check that the node was imported correctly and the subscription is valid
- Make sure the node you want to use is selected in the configuration list. Importing a new subscription doesn’t automatically switch your current connection to a new node.
- Update the subscription in subscription management and check for download failures, empty content, or parsing errors. A subscription URL isn’t the same as a regular informational page link. When copying it, make sure there are no extra spaces or missing characters.
- If the subscription update fails, stop the connection and try again while connected directly. If the provider specifically requires you to use a proxy to update it, follow their instructions.
- Run the connection test or real-connection test provided by the client for the selected node; the exact name varies by version. Then try another node from a reliable source to compare the results.
A successful latency test doesn’t guarantee that web pages will open. Free nodes may be unavailable because they have expired, are congested, or are undergoing maintenance. If you use this site’s free nodes, check the release notes and last updated date. Don’t assume an old subscription will keep working indefinitely.
3. Connected but unable to open web pages: check routing and DNS
First determine whether all apps are affected or just one. Check v2rayNG’s per-app proxy settings to make sure the app in question hasn’t been excluded, then temporarily switch to global proxy mode for testing. If global mode works but rule mode doesn’t, focus on the routing rules. Restore your usual mode when you’re done testing.
If the issue appears to be a domain name resolution failure, note your current DNS settings, then restore the client’s defaults and test again. If Android’s “Private DNS” is enabled, temporarily switch it to Automatic to compare. Don’t change DNS, routing, and nodes all at once—otherwise, even if the problem goes away, it’ll be hard to tell which change fixed it.
4. Use the logs to pinpoint the issue, and reinstall only as a last resort
Clear the old logs, reconnect, and open a web page. Then check the latest errors. “timeout” usually indicates a connection timed out; DNS-related errors point to a problem with name resolution; certificate or TLS errors mean you should check the system time, configuration integrity, and node status. These messages are clues for troubleshooting; a single error doesn’t necessarily reveal the cause.
If the app can’t start its core component or reports an import error, back up your configuration and update the client through the project’s official release channel. Consider reinstalling only after all other checks have failed. When asking for help, provide the client version, network type, and redacted logs. Don’t share your subscription URL, UUID, or full node QR code publicly, as these may expose your access credentials.