What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in the order of phone network, VPN permissions, node subscription, routing, and logs. It applies if tapping Connect does nothing, the app shows connected but webpages won’t load, or some apps can’t access the internet. Don’t keep reinstalling the app; checking each item in turn makes it easier to find the cause.
1. Check your phone’s network and VPN environment
- Close v2rayNG and open a domestic website you can normally access. If that won’t load either, first check for Wi-Fi sign-in requirements, unpaid mobile data charges, or poor signal.
- Switch between Wi-Fi and mobile data and try again. If only one network fails, troubleshoot that network first rather than immediately changing node settings.
- Turn off other VPNs, accelerators, and ad blockers that use local VPN mode. Only one VPN service can usually be active in the same Android user environment, so running multiple services at once can cause conflicts.
- Launch v2rayNG and allow the system’s VPN connection request when you tap Connect. If no prompt appears, open your system’s VPN settings and check whether another app has enabled “Always-on VPN” or is blocking connections without a VPN.
- Enable automatic date and time in system settings. A large time discrepancy can cause TLS verification to fail. There is no need to check the “login status” of any website account here.
2. Make sure the node and subscription are still valid
Open the configuration list and confirm that the selected entry is the node you intend to use, not an old configuration. If you imported it through a subscription, check that the subscription URL is complete in the subscription settings, then update it. Menu names may differ slightly between versions. After updating, check whether the list has changed, and be careful not to accidentally delete a configuration that still works.
A successful subscription update does not mean the node is necessarily usable. Being able to access the subscription URL only means the configuration can be downloaded; the actual node may still be expired or temporarily unreachable. Try another node from a trusted source for comparison. If you’re using one of our free nodes, keep in mind that availability depends on the result of your current connection test.
If you imported the configuration manually from a link, check that the copied text isn’t incomplete and doesn’t contain extra spaces or line breaks. Don’t guess at changes to the port, transport, or TLS options. Instead, reimport the complete link provided by the service.
3. What to check if you’re connected but webpages won’t load
- Make sure you’re using VPN mode rather than a mode that only provides a local proxy; the latter won’t automatically route traffic for all apps.
- Check the per-app proxy settings. If “Proxy only selected apps” is enabled, make sure your browser is on the list. If bypass mode is enabled, check that the browser hasn’t been excluded by mistake.
- Temporarily switch to global proxy mode for comparison. If global mode works but rule mode doesn’t, focus on the routing rules. Restore your original settings after testing.
- If you manually configured Android Private DNS, temporarily set it to Automatic and try again, noting the original setting first. Don’t change multiple DNS and routing settings at once, or you won’t know which change helped.
4. Use the logs to find the cause instead of reinstalling blindly
Open the logs page, clear the old entries, then reconnect and try to visit a webpage. If you see “timeout,” first check your network and whether the node is reachable. “Connection refused” may indicate an issue with the destination port or service status. If you see a certificate error, check the system time, configuration integrity, and client version. Don’t disable certificate verification just to get rid of an error.
If the problem persists, note your Android version, v2rayNG version, network type, and the relevant error message, then contact the node provider. Hide your subscription URL, UUID, and other sensitive information before sharing screenshots. Only consider reinstalling if you suspect the client is damaged. Back up your configuration first, then obtain an installation package that matches your phone’s architecture from a trusted source.