What should you do if v2rayNG won’t connect? This guide walks you through checks in this order: your local network, VPN permissions, node subscriptions, routing, and DNS. It’s for Android users who can’t open webpages after connecting, get timeouts when testing nodes, or can connect over Wi-Fi but not mobile data. Change only one setting at a time and test before moving on so you can identify the cause.
1. Make sure your phone can access the internet
- Disconnect v2rayNG and open a domestic website you can normally access directly. If it won’t load either, first check for Wi-Fi sign-in requirements, an unpaid bill, a weak signal, or router issues.
- Test Wi-Fi and mobile data separately. If only one of them fails, toggle Airplane mode and try again. On public Wi-Fi, complete the web sign-in process first.
- Turn off other VPNs, accelerators, or ad blockers that use a local VPN. Android generally can’t run multiple connections of this type at the same time.
- Turn on automatic time and time zone in your system settings. A significantly incorrect clock can cause TLS certificate validation to fail.
If switching networks fixes the problem, it may be related to restrictions or DNS resolution on the original network. You don’t need to reinstall the app right away. Keep mobile data usage in mind while testing.
2. Check that the VPN is running and has permission
In v2rayNG, select the configuration you want to use, then tap the connect button. The first time you connect, allow the system’s VPN connection request and check that the app shows it’s running. A connected status only means the local VPN has started; it doesn’t mean the remote node is available.
If the connection stops immediately, check whether the system is restricting the app’s background activity, and allow it as needed. If your phone has “Always-on VPN” or “Block connections without VPN” enabled for another app, check for conflicts. Menu names vary by phone brand.
3. Check that the node and subscription are valid
- Make sure you imported a node link or subscription URL supported by the client—not a webpage URL, a link to a QR code image, or incomplete text with extra instructions.
- Update the existing subscription and check for errors. If the update fails, make sure the URL is complete, the subscription hasn’t expired, and your current network can access the subscription service.
- Select a node and run the connection test provided by the client, then try opening a webpage. Different tests measure different things, so a single timeout doesn’t prove that the node is unavailable.
- Test another node from a trusted source that has been updated recently. You can also use this site’s free nodes for troubleshooting, but public nodes may not always be available.
Don’t change parameters such as the port, transport protocol, SNI, or public key at random; they must match the service provider’s settings. Don’t disable certificate verification to hide a connection error. First check the system time, node parameters, and configuration source.
4. What to do if you’re connected but webpages won’t open
First, check the routing mode and per-app proxy settings. If your browser is excluded from the proxy, the connection test may succeed while webpages still won’t load. You can temporarily switch to global proxy mode and test a website that requires a proxy, then switch back to the rules mode that suits your needs.
If only some domains won’t open, check whether you’ve changed the client’s DNS settings or Android’s “Private DNS” setting. Note the original settings, then temporarily restore the defaults or set Private DNS to Automatic and test again. Avoid changing multiple DNS settings at once.
If the problem persists, check the client logs. Timeouts usually require checking both the network and the node; certificate errors call for checking the time and TLS parameters, while resolution errors point to DNS. Hide your subscription link, UUID, and password when asking for help. Share only the client version, network type, relevant error excerpt, and tests you’ve already performed to help pinpoint the issue.