This guide addresses the question “What should I do if v2rayNG won’t connect?” Follow the checklist to troubleshoot your phone’s network, system environment, node details, and client settings. It’s intended for everyday users who can’t connect after importing free nodes or a subscription, or who can connect but can’t open web pages.
1. Check your phone and network environment first
Many connection failures aren’t caused by the node itself, but by network issues or permission problems on your device. Before repeatedly changing configurations, troubleshoot in this order.
- Make sure your network is working: Close v2rayNG and open a domestic website in your browser to confirm that your Wi-Fi or mobile data is working normally.
- Try switching networks: If Wi-Fi doesn’t work, switch to 4G/5G. If mobile data doesn’t work, try another Wi-Fi network. This helps rule out interference from your router, carrier DNS, or campus network restrictions.
- Disable battery saver and background restrictions: In your system settings, allow v2rayNG to run in the background, access the network, and start automatically. Some Android phones disconnect the proxy when the screen locks.
- Check the date and time: A significant discrepancy can cause TLS handshake failures. We recommend enabling “Set time automatically.”
- Make sure no other VPN is running: Android typically allows only one active VPN. Clash, sing-box, and accelerator apps may conflict if they’re running at the same time.
2. Check your nodes, subscription, and import method
If your environment is working normally, check your configuration next. v2rayNG supports protocols such as VMess, VLESS, and Trojan. A missing node parameter can cause connection failures.
- If you use a subscription, tap the menu in the upper-right corner to update it. Make sure you don’t see a parsing error or an empty list.
- If you imported a node manually, check that the address, port, UUID, encryption method, transport protocol, TLS, SNI, and path are all correct and complete.
- After importing a node by scanning a QR code, avoid changing its parameters, especially those related to reality, ws, grpc, and tls.
- Free nodes provided by this site may stop working as availability changes. If one node fails, try another node from the same subscription.
To check whether a node is working, tap “Test all configurations for real connection” in the v2rayNG node list. If all nodes time out, suspect a local network issue or an expired subscription first. If only some fail, those individual nodes are likely unavailable.
3. Common v2rayNG settings mistakes
In v2rayNG, check the following settings: Start with the routing mode set to “Bypass LAN and mainland China addresses.” For remote DNS, use the default value or a common public DNS server. If you’ve changed many advanced settings, try restoring the defaults. When connecting, check whether the key icon appears at the top of the screen. The system VPN is active only once it appears.
If the app says you’re connected but web pages won’t open, try clearing your browser cache, using a different browser, disabling Private DNS, or switching the proxy mode from “Proxy selected apps only” to global mode for testing. If only one app is affected, check v2rayNG’s per-app proxy list to make sure that app hasn’t been excluded.
4. Troubleshooting checklist if you still can’t connect
- Restart v2rayNG, then restart your phone.
- Delete the old node and copy the subscription link again or re-import the node by scanning its QR code.
- Try 2–3 nodes that use different protocols or are in different regions.
- Check the logs for messages such as timeout, handshake failed, connection refused, or no such host.
- Note the error messages and node type to determine whether the issue is related to DNS, TLS, a blocked port, or an unavailable node.
In summary: If v2rayNG won’t connect, don’t assume the node is simply down. Troubleshoot in this order: network environment—system permissions—subscription updates—node parameters—client settings—log messages. This usually helps you pinpoint the problem quickly. If nodes from multiple sources all fail to connect, check your phone’s network, VPN permissions, and time settings first.