What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in this order: local network, VPN permissions, node subscriptions, routing, and DNS. It covers issues like having no internet after startup, node timeouts, and some apps failing to open. Don’t keep reinstalling the app or change several settings at once. Reconnect and test after each step to help pinpoint the cause.
1. Check your network and Android settings
- Close v2rayNG and open a website you can normally access to confirm that Wi-Fi or mobile data is working. If you’re using public Wi-Fi that requires a sign-in, complete the sign-in first.
- Switch between Wi-Fi and mobile data. If you can connect on one network but not the other, investigate restrictions on the network that isn’t working rather than assuming the client is broken.
- Open the system’s “Date & time” settings and enable automatic time and time zone. An incorrect time can cause TLS certificate verification to fail.
- Temporarily turn off other VPNs, accelerators, and ad blockers that use a local VPN. Typically, only one VPN service can be active in the same Android user profile, so running multiple services at once can cause conflicts.
- Start v2rayNG and approve the system’s VPN connection request. If it frequently disconnects in the background, allow it to run in the background in system settings and set its battery usage to “Unrestricted.” Menu names vary by phone brand.
2. Make sure your node and subscription are still valid
Open the configuration list and make sure you’ve selected the node you want to use, rather than just importing it. If you use a subscription, update it from the subscription manager or menu; the option’s location varies by version. If the update fails, first check that the subscription URL is complete and has no extra spaces, and whether your provider requires you to update it on a working network.
When importing a link manually, copy the entire protocol URL and avoid including any explanatory text. The transport method and TLS settings for VLESS, VMess, Trojan, and other configurations should match your provider’s instructions. Don’t disable certificate verification or change key settings just to “see if it helps.”
After connecting, use the client’s connection test and try opening a webpage. Latency results in the list are only a guide and don’t guarantee that every app will work. If only one of several nodes fails, contact the node provider or try another configuration first. Free nodes on this site may also become unavailable or congested, so rely on whether they actually work.
3. If the client connects but webpages won’t open, check routing and DNS
If the interface says you’re connected but only some apps can’t access the internet, check whether “Per-app proxy” is enabled and whether the affected apps are excluded. Also make sure the routing mode suits your needs. To help identify the problem, you can temporarily switch routing to global proxy mode for testing, then restore your usual rules. Don’t confuse this with Android’s per-app VPN settings.
If the logs show a DNS resolution failure, check the client’s DNS settings and Android’s “Private DNS” setting. Note the original settings first, then restore any recently changed options to their defaults and test them one at a time. Change only one setting at a time and keep a record of its original value to make troubleshooting easier.
4. Choose your next step based on the logs
- Timeout or “timeout”: The node may be unreachable, the network may be restricted, or the server may not be responding. Try switching networks and nodes to compare.
- Certificate or TLS error: Check the system time, client version, and configuration. Don’t bypass verification.
- The client stops immediately after startup: Check whether the error mentions configuration parsing or VPN permissions. Try updating the client from a trusted source and importing the complete configuration again.
If the problem persists, note your phone’s operating system, v2rayNG version, network, and error message, then contact your provider for help. Before sharing screenshots or logs, hide your subscription URL, UUID, password, and other credentials.