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 DNS. It covers problems such as webpages not opening after startup, connection timeouts, and some apps being unable to connect. There’s no need to change complex settings right away—adjust one thing at a time so you can identify the cause.
1. First, check that your phone can connect to the internet
Close v2rayNG before testing your basic network connection. If regular webpages won’t open either, troubleshoot your Wi-Fi, mobile data, or network authentication instead of repeatedly switching nodes.
- Disconnect v2rayNG, then use your browser to visit a website you can normally access directly and confirm that your basic connection is working.
- If you’re using hotel, campus, or public Wi-Fi, complete the web login first. Without authentication, you may be connected to Wi-Fi but still unable to access the internet.
- Switch between Wi-Fi and mobile data, then test again. Keep an eye on mobile data usage. If only one network fails, check for network restrictions or router issues.
- Check your system date and time, and consider enabling automatic settings. A significant time discrepancy can cause certificate verification to fail.
2. Check VPN permissions and background restrictions
When you tap the Start button in v2rayNG, Android will usually ask for permission to establish a VPN connection the first time you use it. Allow the request. The VPN icon in the status bar only indicates that the system tunnel has been established; it does not mean the node is connected.
Temporarily disable other VPNs, ad blockers that use local VPN mode, and firewalls to prevent conflicts. If another app has “Always-on VPN” or “Block connections without VPN” enabled, check whether it’s interfering with the current connection. If v2rayNG disconnects shortly after starting, allow it to run in the background and check for battery optimization restrictions. Menu names vary by phone.
3. Check your subscription and node details
- Open subscription management and make sure the subscription URL is complete and contains no extra spaces, then update it. A failed update doesn’t necessarily mean the nodes are invalid; the subscription URL itself may be temporarily inaccessible.
- Select a node and start it, run the connection test provided by the client, then try opening a webpage. Menu names may vary by version, and test results are only a guide.
- Try a node from another trusted source for comparison. If only a few nodes fail, they may be inactive or their configurations may have expired. If all nodes fail, continue checking the client and your network.
When importing VLESS, VMess, or other configurations manually, keep all the parameters provided by the source intact. Don’t guess at port, transport, or TLS settings. Free nodes on this site may also expire or become temporarily unavailable, so check the publication date and usage instructions before importing them again.
4. If you’re connected but webpages still won’t open, check routing and DNS
If only some websites won’t open, temporarily switch the client to global proxy mode for comparison. If they then work, check your original routing rules. If per-app proxying is enabled, make sure your browser or target app hasn’t been excluded.
If the logs repeatedly show domain resolution failures, check whether Android Private DNS is set to a service that your current network can’t reach. Try switching it to Automatic, then test again. Don’t change multiple DNS options at once, and don’t bypass errors by disabling certificate verification.
5. Use the logs to decide what to try next
Keep the error message and troubleshoot accordingly: “timeout” usually means the connection timed out; “connection refused” means the connection was rejected; certificate-related errors call for checking the time, client version, and configuration. These messages can help narrow down the cause, but they don’t identify it on their own.
If the problem persists, update the client through the project’s official release channels, then note the version, network type, and a summary of the error before asking for help. Before sharing screenshots, hide sensitive information such as subscription URLs, UUIDs, and passwords. Don’t share your full configuration.