What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: check your phone, update your subscription, verify your nodes, and compare networks. It will help you distinguish an invalid configuration from system restrictions or a current network issue, and decide when it’s worth switching between Wi-Fi and mobile data. Start with steps that are easy to undo; there’s no need to reinstall the app or reset your network settings right away.
First, check: won’t it start, or can’t you get online after it starts?
If tapping Connect doesn’t bring up the system VPN permission prompt, or the switch turns off immediately, check permissions and app conflicts first. If the VPN icon appears in the status bar but websites still won’t load, check the node, routing, and network next. Showing as connected doesn’t mean the node is working, and a latency test can’t replace trying to open an actual webpage.
- Disconnect v2rayNG and check that your phone can open commonly used websites without it. If the phone itself is offline, first address Wi-Fi sign-in, signal, or mobile data issues.
- Check your system date, time, and time zone. Automatic settings are recommended; an incorrect time can cause certificate verification to fail.
- Pause other VPNs, accelerators, or filtering tools that use a local VPN mode, then reconnect to avoid conflicts over the system VPN connection.
- If it disconnects only after the screen locks, check Android’s battery optimization and background activity restrictions. Allow background activity and test again; you don’t need to disable all security protections.
Update your subscription and check which node is selected
Open subscription management and update your existing subscription, then return to the main screen and confirm that a valid configuration is selected. Menu names may vary by version; look for options such as “Subscription” or “Update.” If the update fails, first check that the subscription link is complete and its source is still accessible. Don’t repeatedly delete all your configurations.
When importing from the clipboard, copy the complete share link without any explanatory text, and make sure you haven’t omitted the trailing parameters. Back up before making changes: keep your original subscription and configuration, and don’t guess at changes to the port, transport, TLS, or server name. Free nodes may temporarily stop working; check the original publishing source for updates. The free nodes on this site should also be treated as subject to actual availability.
Try another recently updated node for comparison. If only one node fails, the node or its configuration is the likely cause. If all nodes fail, check factors that affect them all. Keep the routing mode unchanged during testing so you can identify the cause instead of having to account for several changes at once.
When should you switch networks?
If your phone can access the internet, VPN permissions are in order, the subscription is updated, and multiple nodes still won’t connect, try a same configuration, different network test. Disconnect, switch from Wi-Fi to mobile data or connect to another trusted network, then reconnect using the same node and open the same webpage. Keep an eye on data usage.
- Mobile data works but the original Wi-Fi doesn’t: check whether Wi-Fi requires a web sign-in or has network access restrictions.
- Wi-Fi works but mobile data doesn’t: check the app’s mobile data permissions, data-saving settings, and current signal strength.
- Both networks fail: go back to checking the configuration and node status. This alone isn’t enough to conclude that the network is blocking the connection.
Public, campus, and workplace networks may have usage rules; follow them, and don’t modify the router or try to bypass network management policies without authorization. Switching networks is a way to narrow down the issue, not a guaranteed fix for connection failures.
Still not working? Check the logs and avoid resetting things without a clear reason
Try connecting again, then check the app logs. A timeout needs to be assessed by comparing nodes and networks. For a certificate error, first check the time and configuration. For a name resolution failure, check the domain and your system’s “Private DNS” settings. If you manually specified a Private DNS provider, note the original value and temporarily switch back to automatic settings to test. Don’t disable certificate verification and hope for the best.
When asking for help, include your Android version, v2rayNG version, network type, and a redacted error message. Don’t share your subscription link, UUID, or full configuration publicly. Keep a backup before considering an update from the project’s official release channel. Resetting your network settings to factory defaults should not be your first choice.