What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting problems such as webpages not loading after startup, connection tests timing out, or only some apps being able to connect. Check the network, node, DNS, and browser environment in order. First identify which layer is failing, then adjust the settings to avoid repeatedly switching nodes without finding the cause.
1. Check your network and VPN status
- Disconnect v2rayNG and use your browser to open a website you can normally access directly. If it still won’t load, check your Wi-Fi or mobile data connection, or sign in to the public network.
- Restart v2rayNG, tap Connect, and grant Android’s VPN permission. If the app won’t start, check whether the system is restricting its background activity.
- Temporarily disable other VPNs, network accelerators, and ad blockers that use Android’s local VPN mode. Android usually can’t run multiple services of this type at the same time.
- Switch between Wi-Fi and mobile data once. If the same node only fails on one network, the issue may be related to network restrictions or routing.
The VPN icon only indicates that the tunnel has started; it doesn’t guarantee that the node is working. Continue by checking actual webpage access and comparing the results with the in-app connection test.
2. Check that the node and subscription are valid
Update your subscription, then test a node. A successful subscription update only means the subscription URL could be accessed; it doesn’t guarantee that every node in it is online. Free nodes may have expired or be temporarily unavailable, so test the free nodes provided on this site before relying on them.
- Reimport the original share link to avoid copying it incompletely or manually changing the address, port, UUID, or other parameters.
- Check your phone’s date and time, and enable automatic settings if possible. A significantly incorrect time can cause certificate verification to fail.
- Try a valid node from another trusted source for comparison. If only one node fails, suspect its status or configuration before assuming there’s a problem with your phone.
Don’t disable certificate verification to “fix” the connection.If the logs show a certificate, handshake, or authentication error, verify the node details and use a recent client version from a trusted source. Menu names may vary slightly between versions.
3. Tell an IP issue from a DNS issue
If your browser says it “couldn’t resolve the domain name,” DNS is a more likely cause. A timeout in the logs could also involve the node address, port, or network blocking, so don’t draw conclusions from a single message.
Open Android Settings and search for “Private DNS.” If you previously entered a custom provider, temporarily switch to “Automatic” and try again, noting your original setting first. Also check whether you’ve changed the DNS settings in v2rayNG. Restore a trusted default configuration if needed, and avoid changing multiple options at once.
An unchanged exit IP doesn’t necessarily mean the connection failed. In routing mode, some websites may connect directly. When checking your exit IP, make sure the test page is actually going through the proxy. Don’t test by entering a website’s IP address instead of its domain either; HTTPS certificates and site configuration can skew the results.
4. What to do if only your browser won’t load pages
If other apps work normally, first try opening the page in your browser’s incognito window, then compare the results with another browser. Check whether the browser has custom Secure DNS enabled and, if necessary, temporarily restore the default setting. Also check v2rayNG’s per-app proxy settings to make sure the browser hasn’t been excluded.
If the problem persists, disconnect and restart v2rayNG, then check the latest error in the logs. If you ask for help, provide the client version, Android version, network type, and error message. Don’t share your subscription URL, full node link, or authentication details publicly. Change only one setting at a time and record the result after each test so you can pinpoint the problem and restore the original settings.