What should you do if v2rayNG won’t connect? This guide troubleshoots issues in the following order: your device’s network, system permissions, node subscriptions, routing, and DNS. It covers problems such as websites not loading after startup, connection timeouts, and some apps being unable to access the internet. There’s no need to change server-side settings. Adjust one thing at a time and note the results to avoid making too many changes at once.
1. First, make sure your phone can access the internet
Disconnect v2rayNG, then use your browser to open a domestic website you can normally access. If you still can’t get online with the proxy turned off, troubleshoot your Wi-Fi, mobile data, or account balance first rather than repeatedly switching nodes.
- On public Wi-Fi, complete the sign-in process in the browser if prompted. If no prompt appears, check your system’s network sign-in notification.
- Switch between Wi-Fi and mobile data, and test the same node on each. Note that using mobile data may incur charges.
- Temporarily disable other VPN or proxy apps, as well as ad blockers or firewall apps that use a local VPN.
- Set your phone’s date and time to update automatically. An incorrect time can cause TLS certificate verification to fail.
If the same node works on mobile data but not on Wi-Fi, the issue is likely related to the current Wi-Fi network or carrier route, but that alone doesn’t prove the node is down.
2. Check startup permissions and node details
Open v2rayNG, select the configuration you want to use, and tap the connect button. The first time you connect, allow Android’s VPN connection request. Seeing the VPN icon only means the local VPN has started; it doesn’t mean the remote node is connected.
- If the connection won’t start, check whether another app is using the VPN and whether the system’s always-on VPN or block connections without VPN settings are interfering.
- If the connection drops when the screen locks, allow v2rayNG to run in the background in your system app settings and relax battery restrictions as needed. The menu names may vary between phones.
- For configurations imported from a subscription, refresh it once in subscription management, confirm the update succeeds, and then select a node again.
- For configurations imported from a link, make sure the link was copied in full. Don’t change the address, port, UUID, transport method, or TLS parameters at random.
A successful subscription update doesn’t mean the node is available. It only means the subscription URL could be accessed and the configuration file downloaded. If you’re using free nodes from this site or another source, judge their availability by whether they actually connect at the time.
3. Use connection tests and logs to diagnose the problem
Run the connection test provided by the client, then try opening a webpage. Menu names may vary by version. A latency test isn’t the same as successfully loading a webpage, so don’t draw conclusions from a single number.
- Multiple nodes time out: Switch networks and test again, and check for conflicts with other VPNs.
- Only one node fails: Try another configuration from the same subscription. The original node may be temporarily unavailable, or its details may have changed.
- The log reports a DNS resolution failure: Check whether an unavailable address is entered under your system’s “Private DNS” setting. Temporarily switch back to automatic and test again.
- The log shows a certificate error: First check your phone’s time and the configuration source. Don’t simply enable the option to skip certificate verification.
4. Check routing if some apps won’t open
If your browser works but a particular app doesn’t, check v2rayNG’s per-app proxy list and make sure the app hasn’t been excluded. You can also temporarily switch to the client’s global proxy mode for comparison, then restore your original rules to avoid routing unrelated traffic through the proxy.
Change only one setting at a time, then repeat the same test. If the problem persists, note the client version, Android version, network type, and time of the error, and ask for help with a redacted log. Don’t share your subscription link, UUID, or full node QR code publicly; these may contain access credentials.