What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: phone network → VPN permissions → subscription and nodes → routing and logs. It covers issues such as no internet access after startup, node timeouts, and some apps not opening. You don’t need to change advanced settings right away. Reconnect and test after each step to help pinpoint the cause.
1. Check your phone’s network and VPN setup first
- Close v2rayNG and try opening a domestic website you can normally access directly. If that doesn’t work either, first resolve any Wi-Fi sign-in requirements, mobile data billing issues, or router connectivity problems before troubleshooting the client.
- Switch between Wi-Fi and mobile data once. Public Wi-Fi may require you to sign in through a browser. Complete the sign-in before starting the proxy, so you don’t mistake a blocked sign-in page for a failed node.
- Temporarily turn off other VPNs, accelerators, firewalls, or ad blockers that use local VPN mode. Multiple VPN services usually can’t run simultaneously in the same Android user environment, and conflicts may prevent the VPN from starting or cause it to disconnect immediately.
- Tap the start button in v2rayNG and make sure you’ve allowed the VPN connection request shown by the system. If no prompt appears or authorization fails, search for “VPN” in system settings and check whether another app has enabled “Always-on VPN” or an option that blocks connections without a VPN.
2. Check that your subscription and selected node are valid
Open the node list and make sure you haven’t selected an outdated node. Successfully importing a subscription only means the client has read the configuration; it doesn’t guarantee that the nodes are online. Find the subscription in subscription management and update it. Menu names may vary by version. If the update fails, first check that the subscription link is complete and hasn’t expired, and that your current network can access the subscription URL.
If you’re using free nodes from this site or another source, check when they were published and last updated, as nodes may be temporarily unavailable due to maintenance or congestion. Try another node to compare results first, rather than repeatedly changing settings for the same non-working node. When importing a link manually, copy the entire share link and make sure it hasn’t been split by a chat app or lost its final characters. If the link isn’t recognized, first check whether your client version supports that protocol.
3. Tell the difference between a “test timeout” and no internet access
After selecting a node and starting the service, try opening two different websites, then check the connection test results in the client. A timeout in the latency test doesn’t necessarily mean the node is completely unavailable—the test may fail because its target can’t be reached. Conversely, a latency reading doesn’t guarantee that every website will open.
- Only certain apps can’t connect: Check the per-app proxy settings and make sure the affected app isn’t excluded. If needed, temporarily disable per-app rules and test again.
- Domestic websites work, but your target website doesn’t: Check the routing mode. Temporarily switch to global proxy mode to compare results, then restore your usual rules.
- No websites open after connecting: Stop the proxy and see whether your connection comes back, then try another node. Also set your system date, time, and time zone to automatic to rule out certificate validation issues.
4. Use the logs to narrow down the issue
Clear the old logs, start a new connection, and visit a website. Then check only the errors from that attempt. If you see a timeout, first check your network or try another node. If DNS resolution fails, check the node domain and your current DNS settings; if you previously changed them manually, restore the defaults and test again. For TLS or certificate errors, check the system time, client version, and whether your subscription is up to date.
Don’t disable certificate verification just to get a connection, and don’t change the port, transport, or security settings without a clear reason. If the issue persists, note your Android and v2rayNG versions, the network you’re using, and the exact error message, then contact your node provider. Before sharing a screenshot, hide the subscription URL, UUID, password, and full share link to prevent your credentials from being exposed.