What should you do if v2rayNG won’t connect? This guide walks through troubleshooting in order: phone network → VPN permissions → node subscription → routing and DNS. It covers problems such as losing internet access after startup, node timeouts, and some apps failing to open. You don’t need to reset your phone or modify the server. Change only one setting at a time so you can identify the cause.
1. Check your phone’s network and VPN setup
Don’t delete your configuration right away. First disconnect v2rayNG and make sure your phone can access commonly used websites in your country. If the basic connection isn’t working, troubleshoot Wi-Fi, mobile data, or captive portal sign-in first.
- Test Wi-Fi and mobile data separately. Networks at hotels, schools, and similar locations may require you to sign in through a browser first. Until you do, node tests may time out.
- Turn off any other VPNs, network accelerators, and ad blockers that use the VPN connection. Android generally can’t let multiple apps of this kind manage traffic at the same time.
- Allow the system’s VPN connection request when you start v2rayNG. If no prompt appears and the app won’t start, check your system VPN settings for another app with “Always-on VPN” enabled or an option that blocks connections without a VPN.
- Set your system date and time to update automatically. An incorrect time can cause TLS certificate verification to fail. If the connection drops only after the screen locks, check your battery-saving settings and background activity restrictions.
Confirm that your basic network connection works before checking the node. This helps prevent captive portal sign-in, an unpaid balance, or a weak signal from being mistaken for a configuration problem.
2. Make sure the node is selected and the subscription hasn’t expired
Open the node list and confirm that the selected entry is the node you want to use—not just a configuration you’ve imported but haven’t selected. Menu labels may vary between versions; look for options such as Update Subscription or Test Connection.
- Importing a subscription: Update the relevant subscription, then select a node and test it. If the update fails, check that the subscription URL was copied in full, has no extra spaces, and is still available from its source.
- Importing a link: Copy the complete VLESS, VMess, or other share link again and import it from the clipboard. Don’t guess or manually add parameters.
- Importing a QR code: Make sure the code is complete and clear. After importing, check that the protocol, address, and port match the source’s instructions.
- Switching nodes: Test other nodes from the same source or, if needed, try another trusted source. Free nodes may become unavailable; free nodes provided by this site should also be judged by their actual connection results.
A latency test result doesn’t guarantee that a webpage will load. Some tests only check whether a port is reachable. Start the connection and visit an actual webpage to verify it.
3. If connected but webpages won’t load, check routing and DNS
If the status shows that you’re connected, first check whether per-app proxying is enabled and whether your browser is excluded. Then check the routing rules. Temporarily switch to global proxy mode for comparison. If that works but the original mode doesn’t, focus on the split-routing rules. Restore your preferred mode after testing.
If only some domains won’t load, check whether Android’s “Private DNS” is set to an unavailable custom hostname. Temporarily switch back to automatic and try again. Don’t change the client DNS, system DNS, and routing settings all at once, or it will be hard to tell which change helped.
4. Check the logs and troubleshoot based on the error type
Open the client logs, clear the old entries, and reconnect once. Persistent timeouts usually call for checking the network path, address and port, or node status. Certificate, TLS, and handshake errors call for checking the system time and the imported parameters; the node itself may also be at fault. Don’t bypass errors by disabling certificate verification.
If the issue persists, check the project’s official release channels for a client update. When asking for help, include the client version, network type, and a redacted error log. Don’t share your subscription URL, UUID, or full configuration, as these may expose your credentials.