What should you do if v2rayNG won’t connect? This article walks you through troubleshooting in this order: phone network, VPN permissions, subscription and nodes, then routing and DNS. It covers issues such as no internet access after startup, node tests timing out, and some websites failing to load. Don’t rush to reinstall the app. Change one setting at a time and test after each change to make it easier to identify the cause.
1. Check your phone’s network and VPN permissions
- Close v2rayNG and try visiting a website that normally works without a VPN. If it won’t load either, first check for Wi-Fi sign-in requirements, mobile data issues, or a weak signal. On public Wi-Fi, complete the sign-in process in your browser first.
- Switch between Wi-Fi and mobile data, then test the same node again. If it fails only on one network, that network may be restricting the connection; this doesn’t necessarily mean the client is at fault.
- Pause other VPNs, accelerators, and ad blockers that use Android’s local VPN mode. Android generally allows only one app at a time to use the VPN connection.
- When starting v2rayNG, allow the system’s VPN connection request. If you previously denied it, tap Start again. Also check your system settings to see whether another app has “Always-on VPN” enabled or is set to block connections without a VPN.
- Set your system date and time to automatic. A significant time discrepancy can cause TLS verification to fail. If the connection drops only after you lock the screen, check background activity and battery optimization restrictions.
The VPN icon only indicates that the local tunnel has started; it doesn’t guarantee that the remote node is available. Open a webpage to verify that the connection actually works.
2. Check for subscription updates and verify your nodes
Update your subscription in subscription management, and check for download failures, empty content, or parsing errors. Menu names may vary by version. A failed subscription update and an inability to connect to a node are two different issues: for the former, check the subscription URL and your current network; for the latter, continue by checking the node itself.
- Make sure you’ve imported the complete subscription URL or node link, with no extra spaces, line breaks, or missing characters. Don’t use a webpage that describes the subscription in place of the subscription URL.
- If the connection stopped working after an update, select a node from the list again to make sure you aren’t still using an expired configuration.
- Test a few different nodes and try opening a webpage. Latency results can help with troubleshooting, but they don’t guarantee that every website will be accessible.
- If the service provider has changed the address or transport settings, reimport the original configuration. Don’t guess at changes to the port, UUID, TLS, or transport method.
Free nodes may expire or be temporarily unavailable. If you’re using free nodes from this site or another source, check for update notices. Don’t publicly share complete links or subscription QR codes that contain credentials.
3. What to do if the app starts but webpages won’t load
First, make sure the current mode isn’t “Direct,” then temporarily switch to Global Proxy mode for testing. If Global Proxy works but rule-based mode doesn’t, focus on checking the routing rules. When you’re done testing, switch back as needed to avoid routing unrelated traffic through the proxy.
If only certain domains won’t load, check whether the DNS settings have been changed, and try restoring the client’s default settings first. Don’t change DNS, routing, and node parameters all at once, or it will be difficult to tell which change made a difference. The problem may also be with the website itself, so test several websites to compare.
4. Use the logs to narrow down the problem
Open the client logs, reconnect, and check the latest error. “timeout” usually indicates a connection timeout; “connection refused” may point to the destination port or service status; for TLS or certificate errors, first check the time, node domain, and configuration for completeness. These messages aren’t definitive on their own, so consider them alongside the results of trying a different network or node.
If the problem persists, note the client version, Android version, network type, and a redacted error message, then contact your node provider. If you need to upgrade, download the client from the project’s official release channel. Don’t install modified versions from unknown sources or disable certificate verification while troubleshooting.