What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting your browser, system permissions, DNS, and node routes—in that order—to help you tell whether the client isn’t routing your traffic or the node is unavailable. The steps prioritize low-risk changes that you can undo. There’s no need to factory-reset your phone or clear your configuration right away.
1. Check the connection status and keep your existing configuration
Before you begin, note your current node, routing mode, and DNS settings. Take screenshots before making changes so you can restore them later. Change only one setting at a time, and test before moving on to avoid losing track of the cause.
- Stop v2rayNG and confirm that your phone can access domestic websites normally. If they won’t load either, troubleshoot Wi-Fi, mobile data, or network sign-in first.
- Reconnect. The first time you use the app, allow Android’s VPN connection request and confirm that the VPN status appears in the system UI.
- Turn off other VPNs, proxies, or ad-blocking apps that use local VPN mode to avoid conflicts over the same connection.
- In your system app settings, allow v2rayNG to run in the background. If it only disconnects after the screen locks, check battery optimization restrictions.
2. Use a browser to check for isolated issues
Keep the connection active and open a domestic website and an international website that you know is accessible. If only one page won’t load, don’t assume the node is down. Try another browser or an incognito window to rule out interference from the cache, extensions, or an old session.
Check whether your browser has “Secure DNS” enabled separately or is using a third-party DNS resolver. If you set this manually, temporarily restore the default setting and test again, making a note of the original value. Don’t disable certificate verification or install an unfamiliar root certificate as a troubleshooting step. If you see a certificate error, first check that your phone’s date, time, and time zone are set to sync automatically.
3. Check DNS and routing without blindly copying settings
If the logs repeatedly show errors such as domain name resolution failures or DNS timeouts, stop the connection and temporarily change your phone’s “Private DNS” setting from a custom hostname to “Automatic,” then reconnect and test. Menu names vary by Android version. If this doesn’t help, restore the original setting.
Next, check v2rayNG’s routing settings. If you’re using custom rules or per-app proxying, make sure the browser hasn’t been excluded. You can temporarily switch to the client’s built-in global proxy routing mode for testing, then switch back afterward. DNS options vary by version, so don’t copy a complete set of settings from an unfamiliar guide, and don’t change DNS in your phone, browser, and client all at once.
4. Check your subscription and node routes last
- Update once using your existing subscription URL and check whether the update fails. If it does, keep your current nodes; don’t delete the subscription first.
- Select a node and run the connection test provided by the client. A successful latency or TCP test doesn’t guarantee that websites will load, so verify by opening a website too.
- Try other nodes in the same subscription, then test over both Wi-Fi and mobile data to distinguish a node issue from a restriction on your current network.
- Check the logs for timeouts, connection refusals, or TLS handshake failures. Note when they occurred and which client version you’re using, then report the issue to your node provider.
Free nodes may become temporarily unavailable due to expiration, congestion, or route changes. Whether you import nodes from this site or elsewhere, verify them one by one. Don’t share your subscription URL or a full node QR code publicly. Before sharing a screenshot for help, hide the server address, user identifier, and subscription token. If several trusted routes fail across different networks, consider backing up your configuration and updating the client from the project’s official release channel.