What should you do if v2rayNG won’t connect? This guide troubleshoots the issue in the order of “phone and network environment—node configuration—app settings—log verification,” addressing problems such as no internet access after startup, node timeouts, and some apps bypassing the proxy. There’s no need to reinstall repeatedly or change settings at random. Adjust only one setting at a time to make it easier to identify the cause.
1. Check your phone and network environment
- Close v2rayNG and make sure your browser can open domestic websites. If you can’t access the internet at all, first check for Wi-Fi sign-in requirements, mobile data issues, or an unpaid bill.
- Switch between Wi-Fi and mobile data, then try again. If the issue occurs only on one network, it may be related to that network’s access restrictions, DNS, or authentication status.
- Pause other VPNs, accelerators, firewalls, and ad-blocking apps that use a local VPN. Android generally cannot run multiple services of this kind at the same time.
- Turn on automatic date, time, and time zone settings. An incorrect clock may cause TLS certificate verification or connection authentication to fail.
- When starting v2rayNG, allow the system’s VPN connection prompt. If no prompt appears and startup fails, check whether another app is occupying the system VPN settings.
First confirm that your basic network connection works, then troubleshoot the node. The VPN icon in the status bar only indicates that the local VPN has started; it doesn’t mean the remote node is reachable.
2. Check that the node and subscription are valid
Select the node you want to use and run the connection test provided by the client; menu names may vary between versions. A timed-out test doesn’t necessarily mean the node is permanently unavailable, so also check whether websites actually load.
- If you use a subscription, update it first, then select the node again. If the update fails, check that the subscription URL is complete and hasn’t expired, and that your current network can access the subscription service.
- If you imported a node using a share link, make sure the copied content wasn’t truncated. It’s best to reimport the original link rather than guessing and changing the UUID, port, transport method, or TLS parameters.
- Test another node from a reliable source for comparison. If only one node fails, it’s likely unavailable or incorrectly configured. If they all fail, recheck your phone and app settings.
When using free nodes listed on sites such as freevpn-x.com, also check the update date and usage instructions. Free nodes can become unavailable, and an old link is not guaranteed to keep working.
3. Check routing, per-app proxy settings, and DNS
If the node connects but webpages won’t open, check whether per-app proxying is enabled and whether the browser you’re using is excluded. You can temporarily disable per-app restrictions and switch to the client’s global proxy mode for comparison. Once you’ve identified the issue, restore your usual rules.
If only certain domains won’t open, check your DNS settings. Note the current settings, restore the client’s default DNS configuration, and try again. If your phone uses a custom “Private DNS” setting, temporarily switch it to automatic for comparison. Don’t change multiple DNS or routing options at once, or it will be hard to tell which setting made a difference.
If the connection drops when the screen is locked, allow v2rayNG to run in the background in your system’s battery settings and disable battery restrictions for the app. The exact settings path varies by phone brand.
4. Use logs to narrow down the issue
Open the app logs, clear the old entries, then reconnect and try opening a webpage. If you see a timeout, focus on network reachability and node status. If you see a certificate or TLS error, check your system time and node parameters. If you see a DNS resolution error, focus on your DNS settings. Don’t disable certificate verification just to get connected.
If the issue persists, check the version against the project’s official release channels and update after backing up your configuration if needed. When asking for help, provide the client version, network type, and redacted logs. Don’t share your subscription URL, UUID, or full share link.