What should you do if v2rayNG won’t connect? This practical checklist helps you distinguish between local network issues, VPN permissions, inactive nodes, and proxy settings. Whether nothing happens when you tap Start or it says you’re connected but webpages won’t load, work through the checks in order to avoid repeatedly reinstalling the app or changing settings blindly.
1. Check your network and phone settings first
Before troubleshooting, close v2rayNG and make sure you can open common domestic websites on your phone. If your current Wi-Fi network requires you to sign in through a web page, complete that step first. Don’t mistake a login page on a public network for a node failure.
- Test both Wi-Fi and mobile data. If only one connection fails, first check its authentication status, access restrictions, or signal strength.
- Pause other VPNs, accelerators, ad blockers that use local VPN mode, and VPNs in your work profile. Android generally allows only one active VPN service per user, so multiple tools may compete for the connection.
- Turn on automatic date, time, and time zone in system settings. An incorrect clock can cause secure connection checks to fail.
- Allow the system’s VPN connection prompt when starting v2rayNG. If the app often disconnects when sent to the background, also check battery optimization and background activity permissions.
2. Make sure the node or subscription is still valid
If the app starts but no websites are accessible, first make sure you’ve selected the node you want to use, then update the subscription from subscription management or the relevant menu. Menu names may vary between versions. If the update fails, check the subscription URL and your current network first; don’t delete all your configurations right away.
- Check whether the subscription has expired or been disabled, or whether some characters were omitted when you imported it. Subscription URLs often contain access credentials, so don’t share them publicly.
- Copy the full node link again from a trusted source and import it from the clipboard or scan its QR code to avoid missing characters when entering it manually.
- Test another node from a reliable source for comparison. You can also use a free node from this site for a temporary comparison, but availability may vary and continuous uptime isn’t guaranteed.
- Check whether the current client supports the node protocol. If you see a field error after importing, update the client through the project’s official release channel rather than installing an unofficial modified version.
A latency test returning a value doesn’t mean webpages will necessarily load. The test may work differently from actual browsing, so also check whether the site opens in your browser.
3. Connected, but webpages still won’t load
Check the routing or split-tunneling mode, and temporarily switch to global proxy mode for comparison. Once you’ve identified the issue, switch back to your usual routing mode. If global mode works but split tunneling doesn’t, focus on the rules instead of repeatedly changing nodes.
- Check whether per-app proxying is enabled. If your browser is excluded, its traffic won’t go through the proxy.
- If the logs show a domain name resolution failure, restore the client’s default DNS settings and check whether Android’s “Private DNS” is set to a custom address that can’t be reached.
- If only one website is affected, try other sites to rule out maintenance, regional restrictions, or account verification issues on the target site.
4. Use the logs to decide what to do next
Open the app logs and reproduce the connection failure once. A timeout usually calls for checking the network and whether the node is reachable. A connection refusal may mean the remote service is unavailable. For a certificate error, check the device’s time, node details, and client version. Don’t turn off certificate verification just to get rid of an error.
When asking for help, include the client version, Android version, network type, and error details with sensitive information removed. Don’t publicly share your full subscription, node credentials, or QR code. Change one setting at a time and note the result; this usually makes it easier to find the cause than changing several settings at once.