What should you do if v2rayNG won’t connect? This guide troubleshoots the issue in order: your network, VPN permissions, node subscriptions, routing, and logs. It’s for cases where you can’t open webpages after starting the app, node tests time out, or some apps don’t use the proxy. Don’t reinstall repeatedly. Change just one setting at a time so you can identify the cause.
1. Check your phone’s network and operating environment
- Close v2rayNG and try visiting a website that normally opens directly. If it still won’t load, resolve any Wi-Fi sign-in, mobile data payment, or signal issues before testing the proxy.
- Switch between Wi-Fi and mobile data to test. If the same node fails only on one network, the cause may be network restrictions or a DNS resolution issue, rather than a client fault.
- Turn on the system setting for automatic date and time. A significantly incorrect time can interfere with TLS certificate validation and cause a handshake failure.
- Turn off other VPNs, accelerators, and ad blockers that use Android’s local VPN mode. Android generally can’t run multiple services of this type at the same time.
- When starting v2rayNG, allow the system to create a VPN connection. If no prompt appears, check the system’s VPN settings to see whether another app has enabled “Always-on VPN” or is blocking connections without a VPN.
v2rayNG usually doesn’t require an account to use. If your subscription provider requires you to sign in, do so through its trusted website. Don’t enter your account credentials into an unfamiliar “repair tool.”
2. Make sure the node imported correctly and the subscription is still valid
- Make sure the node you want to use is selected in the list; importing it alone isn’t enough. After tapping Start, check that the client indicates the service is running.
- Copy the full link again from its original source, then import it from the clipboard. Missing parameters or links truncated by a chat app can cause VLESS, VMess, and other connections to fail.
- If you’re using a subscription, check its address in the subscription settings, then update it. If the update fails, first resolve the subscription retrieval issue. Even a successful update doesn’t mean every node is working.
- Test two or three different nodes individually, preferably with a real connection test, and try opening a webpage. A single latency figure doesn’t prove that webpages will load, and a test timeout alone doesn’t identify the cause.
Don’t change the port, transport, SNI, or TLS settings arbitrarily. These values must match the node information; follow the provider’s instructions. When using free nodes from this site or other sources, check the last-updated and availability notices, and don’t share your full subscription address with strangers.
3. What to do if it shows as connected but webpages won’t open
Temporarily switch the client to global proxy mode, then visit the target website. If global mode works but your previous mode doesn’t, check the routing rules and whether per-app proxying is enabled with your browser left out. Menu names may differ slightly between versions.
If the connection works but domain names don’t resolve properly, first revert any recent DNS changes. If custom “Private DNS” is enabled on your device, temporarily set it to automatic and compare the results. Adjust one setting at a time and note its original value. Don’t change the node, DNS, and routing mode all at once, or it will be difficult to pinpoint the cause.
4. Check the logs to decide what to try next
Open the client logs and find the entries from when startup or access failed. “Timeout” usually means the connection didn’t complete in time. For TLS or certificate errors, first check the system time and node settings. For “connection refused,” first check the address, port, and service availability. These messages are clues, not conclusive diagnoses.
If multiple nodes fail on different networks, consider updating the client through the project’s official release channel. Back up your configuration before trying again. When asking for help, provide the client version, Android version, network type, and redacted logs. Hide your UUID, subscription link, and password; this is safer than sending your full configuration.