What should you do if v2rayNG won’t connect? This guide helps you troubleshoot in order: local network, VPN permissions, node subscriptions, routing, and DNS. It covers issues such as webpages not loading after startup, node timeouts, and Wi-Fi working while mobile data does not. First make sure your regular internet connection is working, then check the client to avoid repeatedly importing nodes without finding the cause.
1. First check whether the problem is with your current network
- Stop v2rayNG and open a website you can normally access without a proxy. If it still won’t load, first check Wi-Fi sign-in, mobile data settings, or your data plan status.
- Switch between Wi-Fi and mobile data. After each switch, reconnect and visit the same webpage. If only one network fails, focus on restrictions affecting that network; there’s no need to reinstall the app right away.
- Public Wi-Fi may require you to sign in through a webpage. Disconnect the proxy, complete authentication, and then start v2rayNG. Company or school networks may also restrict certain connections, so follow their network usage policies.
- Set your system date, time, and time zone to automatic. A significantly incorrect time can cause TLS verification to fail.
2. Check VPN permissions and app status
When you start v2rayNG, allow the VPN connection request from Android. If the connection doesn’t start successfully, search for “VPN” in system settings and check whether another VPN, ad blocker, or firewall is using the connection. Similar apps can conflict, so pause them and try again.
If the connection works at first but drops after you lock the screen, allow background activity in the app’s battery settings and remove any excessive battery-saving restrictions. The settings path varies by device brand. A VPN icon in the status bar only means that a tunnel has been established; it doesn’t guarantee that the node is working, so verify by opening a webpage.
3. Check nodes, subscriptions, and test results
- Check which configuration is selected. If you’ve imported multiple nodes, make sure the one you want to test is actually enabled.
- If you use a subscription, update it and check the result. If the update fails, check whether the subscription URL is complete or has expired. A failed update doesn’t mean all existing nodes are unusable.
- Use the client’s connection or latency test, then try opening a webpage. A test timeout is just a clue; it doesn’t prove on its own that the node is unusable.
- Try another node from a trusted source for comparison. Free nodes may stop working temporarily. If you get nodes from this site, check the publication date and supported clients as well; one successful connection isn’t a long-term guarantee.
When importing manually, check that the link hasn’t been truncated and that the protocol type is supported by your current version. If needed, update the client through the project’s official release channel, and back up your configuration first. Don’t change the port, transport method, or TLS parameters based on guesswork.
4. What to do if the connection succeeds but webpages won’t load
First, make sure you’re using VPN mode rather than local proxy mode, which is intended for other apps to use. If only some websites are inaccessible, temporarily switch to global routing for comparison, then restore the appropriate split-tunneling mode after testing. If global routing works but split tunneling doesn’t, check the routing rules and app exclusion list.
If the logs show a domain resolution error, check your DNS settings. Note the original values and change only one setting at a time. Don’t change DNS, nodes, and routing all at once, or it will be difficult to pinpoint the cause. Don’t disable certificate verification just to get a connection, as this reduces connection security.
5. What information to record if the problem persists
Open the logs and note when the error occurred, the client version, the network type, and any messages such as timeout, resolution failure, or handshake failure. When asking for help, hide sensitive information such as subscription links, UUIDs, passwords, and server addresses. Change only one setting at a time as you work through the steps above; this usually makes it easier to tell whether the problem is with the network, node, or client settings.