What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in the order of “phone network → app permissions → node configuration → routing and DNS” to resolve issues such as losing internet access after startup, node tests timing out, or certain apps not opening. You usually don’t need to reinstall repeatedly. First identify the scope of the problem, then make changes one at a time to find the cause.
1. Check your phone’s network and operating environment
- Disconnect v2rayNG and open a regular webpage to confirm that Wi-Fi or mobile data is working. If the hotel, campus, or public Wi-Fi requires you to sign in through a webpage, complete that authentication first.
- Switch between Wi-Fi and mobile data, then connect to the same node. If the connection fails on only one network, investigate restrictions on that network before changing node settings.
- Turn off other VPNs, accelerators, and ad blockers that use a local VPN. Android usually can’t let multiple apps of this type manage the connection at the same time.
- Set the system date, time, and time zone to automatic. An incorrect time can cause TLS certificate verification to fail.
- Check whether “Always-on VPN” or “Block connections without VPN” is enabled for another app. If so, resolve the conflict first, then restart v2rayNG.
The VPN icon in the notification bar only means that the system tunnel has been established; it doesn’t mean the node is reachable. When you start the app for the first time, allow the VPN connection request. If the connection often drops after the screen locks, allow v2rayNG to run in the background and check for battery optimization restrictions.
2. Make sure the node and subscription are valid
- Select the configuration you want to use, then start the connection. If you’ve imported multiple nodes, make sure you haven’t selected an old configuration.
- If you use a subscription, open the subscription group settings, verify that the address is complete, then update the subscription. Menu names may vary between versions. If the update fails, check whether the link has expired or whether you need to sign in to the provider’s website to get a new one.
- If you received a single vmess, vless, or trojan share link, import it from the clipboard or by scanning its QR code. Don’t enter it as a subscription address.
- Run the connection test in the app and compare the results with another valid node. Don’t rely on the latency number alone—open a webpage after connecting to verify that it works.
A successful subscription update doesn’t mean that every node in it is available. Free nodes may stop working or be affected by your network environment. If you use the free nodes on this site, also check when they were last updated. Don’t change the port, UUID, transport, or TLS settings at random; get a complete configuration instead.
3. If connected but webpages won’t open, check routing and DNS
If only certain websites or apps fail, first check whether per-app proxying is enabled and whether the app in question is excluded. You can also temporarily switch to global proxy mode for comparison. If that fixes the problem, review your original routing rules, then switch back as needed after testing.
If the logs show a domain name resolution error, note your current settings, then check for conflicts between the DNS options in v2rayNG and Android’s “Private DNS.” Temporarily set Private DNS to Automatic to test. Change only one setting at a time, and revert it if it doesn’t help. Don’t replace multiple DNS settings at once.
4. If it still fails, use the logs to narrow down the problem
Clear the old logs, reconnect, visit a webpage once, then check the new errors. A timeout is often caused by a network issue or an unreachable node; “connection refused” may mean the target port is rejecting the connection; a certificate error may point to an incorrect time or configuration. Error messages are clues, not definitive diagnoses on their own.
Finally, make sure the client came from an official project release channel, and update it if necessary after backing up your configuration. When asking for help, include the app version, Android version, network type, and redacted logs. Don’t share your full subscription address, UUID, or QR codes containing credentials.