If v2rayNG shows that it’s connected but webpages won’t load, or tests keep timing out, should you try another node or switch networks first? This guide walks you through checking Android permissions, your subscription, nodes, and network conditions in order of risk to help identify the cause—and avoid repeatedly reinstalling the app, clearing data, or changing system settings.
1. First, check whether your internet is down or the proxy isn’t working
Stop v2rayNG and try opening a website you can normally access directly. If it still won’t load, first check whether you need to sign in to the Wi-Fi network, whether mobile data is enabled, and whether your data plan is active. There’s no need to keep switching nodes until your basic internet connection is working again.
If direct access works, start v2rayNG. A VPN icon only means that the system tunnel has been established; it doesn’t mean the node is working. Check the connection logs and try opening a webpage to verify the connection. A single latency test can’t diagnose every connection issue on its own.
2. Complete these five checks in order
- Check VPN permissions and conflicts: When prompted, allow Android to establish a VPN connection. If you’re using another VPN, an accelerator, or a blocking tool that relies on a local VPN, pause it before starting v2rayNG.
- Check which node is selected: Make sure the selected configuration is the node you intend to use. If you imported it manually, check that the address, port, user ID, and transport settings are all present. If you’re unsure, reimport the original link rather than guessing at changes to the settings.
- Update your subscription: Update the relevant subscription in subscription management and check for errors. A failed update doesn’t necessarily mean your existing nodes are no longer working. Don’t delete all your configurations right away, or you could lose ones that still work.
- Compare with another trusted node: If only one node fails on the same network, it may be offline, its configuration may have changed, or access may be restricted. Free nodes on this site may also change, so check whether they actually connect.
- Check the time and routing: Turn on automatic date and time in your system settings. If only some apps can’t connect, check whether per-app proxying or bypass rules are enabled and make sure the affected apps aren’t excluded.
3. When should you switch networks?
If direct access works, VPN permission is enabled, and multiple nodes fail to connect, compare the connection on another network. Keep the same node and settings, and switch only between Wi-Fi and mobile data to avoid changing multiple variables at once.
- Wi-Fi fails, but mobile data works: The issue may be related to the Wi-Fi network’s sign-in requirements, network policies, or connection. Complete any sign-in steps required on public Wi-Fi. Follow your organization’s rules on workplace or campus networks.
- Mobile data fails, but Wi-Fi works: Check whether v2rayNG is restricted from using mobile data and whether Data Saver is enabled in your system settings.
- Both networks fail: Recheck the node, configuration, or client for problems rather than immediately concluding that one of the networks is blocking access.
Stop the connection before switching networks, then reconnect afterward. Testing on mobile data uses your data allowance. Don’t disable your Wi-Fi password or system security protections, or install certificates from unknown sources, just to troubleshoot.
4. If it still fails, check the logs before asking for help
Open the client logs and note the time of the test and any error keywords. “timeout” usually means the connection wasn’t established within the allotted time. For certificate-related errors, first check the system time and configuration. Parsing errors may involve the domain name or DNS. Similar messages can have different causes, so don’t draw conclusions from a single word.
Don’t try to fix the issue by disabling certificate verification. If you need to report the problem, include the client version, Android version, network type, and test results. Before sharing a screenshot, hide your subscription URL, user ID, and node credentials. Only consider updating from a trusted release channel after confirming a compatibility or installation issue, and back up your configuration first.