What should you do if v2rayNG won’t connect? This guide troubleshoots issues in the order of “basic network, VPN permissions, node subscription, routing, and DNS” to help you determine whether the problem is with your phone’s network, the client settings, or an expired node. It applies to Android users experiencing connection timeouts, being unable to browse the web after starting the client, or certain apps being unable to access the internet.
1. First, make sure your phone can access the internet
Stop v2rayNG and open a website you can normally access directly. If it still won’t load with the proxy turned off, first check your Wi-Fi, mobile data, account balance, or public network login. Don’t rush to change node settings.
- Test two different websites in your browser to rule out an issue with a single site.
- On public Wi-Fi, complete the web login first; if necessary, disconnect and reconnect.
- Switch between Wi-Fi and mobile data, then test the same node again. Keep in mind that mobile data usage may incur charges.
- Set your phone’s date, time, and time zone to automatic. An incorrect time may cause TLS verification to fail.
If the same node works on mobile data but not on Wi-Fi, the problem is usually related to the current network, though differences in DNS or network routing may also be involved. Don’t draw a conclusion based on just one test.
2. Check VPN permissions and background restrictions
When you start v2rayNG, allow the VPN connection if prompted by the system. Then check whether the client shows that it is running and whether a VPN icon appears in the system interface; its location may vary by phone.
Temporarily turn off other VPNs, ad blockers that use local VPN mode, and firewalls to prevent them from competing for the system VPN connection. If the connection always drops after the screen locks, allow v2rayNG to run in the background in your system app settings and relax its battery restrictions as needed. Menu names vary by device, so you don’t need to follow the exact steps for another phone.
3. Make sure the node and subscription are working
- Make sure you’ve selected the node you want to use, rather than merely importing it.
- Update the subscription in subscription management and check for errors. An update failure doesn’t necessarily mean the existing nodes are unavailable, so test them separately.
- Try another node from a trusted source for comparison. Free nodes may expire or become temporarily unreachable; test our free nodes to confirm whether they work.
- If you imported a node from a link or QR code, reimport the original content rather than guessing at changes to the port, transport, or TLS settings.
A successful latency test doesn’t guarantee that web pages will load, and a single timeout doesn’t necessarily mean the node is permanently unavailable. Check actual website access alongside the client logs.
4. What to check if you’re connected but can’t open web pages
First, check the routing mode and per-app proxy settings. If only one app can’t access the internet, check whether it’s excluded from the proxy. If only some websites are affected, temporarily switch routing modes to compare results, then restore your original settings after testing.
If the logs repeatedly show domain resolution failures, check the client’s DNS settings and whether Private DNS is manually enabled on your system. Note your original configuration, then try switching back to automatic settings. Avoid changing several settings at once, or it will be difficult to identify the cause.
In logs, timeout usually means the connection timed out while waiting; connection refused may point to an issue with the destination port or service status; TLS- or certificate-related errors call for checking the system time and node settings. An error message is a clue, not a definitive diagnosis. If you ask for help, provide the client version, network type, and redacted logs. Don’t share your subscription address, UUID, or complete node link.