What should you do if v2rayNG won’t connect? This guide helps you distinguish between a local network outage, VPN permission issues, an unavailable node, and DNS problems. It applies to Android phones that can’t load web pages after startup, time out during node tests, or work over Wi-Fi but not mobile data. Follow the steps in order, changing only one setting at a time so you can identify the cause.
1. Make sure your phone can access the internet
- Disconnect v2rayNG and open a website you can normally access directly in your browser. If it won’t load, troubleshoot your phone’s network first instead of switching nodes.
- If you’re using Wi-Fi, check whether you need to sign in through a web page. Public networks often require authentication before you can access the internet.
- Turn off Wi-Fi, switch to mobile data, and test again. You can also test in the reverse direction afterward. If only one network fails, the issue is more likely related to that network’s restrictions or connection status.
- Turn Airplane mode on and then off, and wait for the network to reconnect. Also check your phone’s date, time, and time zone. We recommend enabling automatic settings to prevent time discrepancies from affecting TLS verification.
Test your direct connection first, then test the proxy. A working direct connection confirms that your phone has basic internet access, but it does not guarantee that the current network can reach the node server.
2. Check VPN permissions and client status
First, disconnect any other VPNs, accelerators, or filtering tools that use local VPN mode. Android typically can’t run multiple services of this type at the same time for the same user. When starting v2rayNG, allow the VPN connection request that appears. If you accidentally denied it, stop the connection and try again.
Open your system settings to check whether v2rayNG is allowed to use Wi-Fi and mobile data, and check for restrictions on data saving, background data, and battery optimization. If the connection works at first but drops when the screen locks, allow background activity and consider relaxing battery restrictions. Menu names vary by phone, so refer to the options on your device.
The VPN icon in the notification bar only means the local service has started; it does not mean the node is connected. Confirm the connection by visiting a website or running a test in the client.
3. Check the node, subscription, and routing mode
- Make sure the selected node is the one you intend to use; importing a node alone doesn’t select it. If you use a subscription, try updating it and check for errors.
- Import the configuration again from its original source to rule out missing characters, truncated links, or leftover settings from an old configuration. Don’t change the address, port, UUID, transport method, or TLS parameters without a reason.
- Test another recently updated node from a trusted source. Free nodes may expire or become temporarily unavailable, so one failed node doesn’t mean the client is broken.
- Check your routing and per-app proxy settings. If only one app won’t load, make sure it hasn’t been excluded. You can briefly switch to global proxy mode for comparison, then restore your usual rules.
4. Use test results and logs to pinpoint the issue
If the TCP test returns a result but actual access still fails, the issue may be authentication, TLS, transport settings, or DNS. A reachable port doesn’t mean the proxy is fully working. If multiple nodes all time out over Wi-Fi but work over mobile data, troubleshoot the current Wi-Fi network first instead of repeatedly reinstalling the app.
Open the client logs, reconnect, and check the latest errors. A timeout often points to a network path issue or an unresponsive server; for authentication failures, check the node details first. If you see a certificate error, check the time and configuration. Don’t disable certificate verification just to get rid of the error. For DNS resolution failures, check the DNS settings as described in the client’s documentation. Change only one setting at a time and keep a record of the original value.
Before asking for help, note your network type, client version, and the exact error message, and describe what happens when you switch networks or nodes. Hide your subscription URL, UUID, and other sensitive details in screenshots. Get updates from the project’s official release channels, and avoid modified versions from untrusted sources.