This article addresses the common question “What should I do if v2rayNG won’t connect?” and is intended for everyday users who don’t want to deal with complicated settings. Follow the steps below, starting with the least risky checks: first check your nodes and subscription, then your phone’s network, system permissions, and client settings. Only then consider switching network environments.
1. Start with basic, low-risk checks
A v2rayNG connection failure doesn’t necessarily mean the node is down. It could also be caused by the time settings, permissions, or a change in network. Avoid deleting configurations unnecessarily; instead, check each item in order.
- Check your phone’s time: Open system settings and enable “Set time/time zone automatically.” A significant time discrepancy can cause TLS handshake failures.
- Make sure v2rayNG has VPN permission enabled: The first time you connect, your system will show a VPN request. Tap Allow. If you declined by mistake, restart the app and try connecting again.
- Test another node: If you’ve imported multiple VLESS, VMess, or Trojan nodes, try 2–3 nodes from different regions or on different routes.
- Update your subscription: Open v2rayNG, go to the subscription group, and tap Update subscription. This site also collects free nodes; we recommend refreshing the subscription before using them.
- Check the error message: Long-press the node or open the log, and look for keywords such as timeout, connection refused, or TLS handshake failed.
2. Check that the client settings haven’t been changed accidentally
Many connection issues stem from changed settings. If you’re an everyday user, it’s best to keep the defaults and avoid enabling advanced features unless you need them.
- Routing mode: Prefer “Bypass LAN and mainland China addresses” or the default mode to avoid rule conflicts.
- Local DNS: If webpages won’t open after connecting, try switching your system DNS or turning off any unfamiliar DNS options in the app.
- Allow LAN connections: This generally isn’t needed on a regular phone and can create unnecessary security risks.
- Per-app proxy: If per-app proxy is enabled, make sure apps such as your browser, Telegram, and YouTube are selected.
If you’re not sure what you changed, export any important nodes, clear v2rayNG’s data, and then import your subscription again. This is a relatively safe way to restore the app.
3. When to switch network environments
If none of your nodes connect and the configuration looks correct, check whether your current network is causing the problem. Switching network environments is a low-risk step that won’t affect your node configuration, making it a good troubleshooting option.
Test in this order: first switch from Wi-Fi to mobile data. If you’re using a campus network, company network, or public Wi-Fi, try a home broadband connection or a mobile hotspot instead. If mobile data still doesn’t work, toggle airplane mode off and on to reconnect to the network. Some networks restrict UDP, TLS, or specific ports, which may cause a node to stay on “Connecting” or disconnect shortly after.
4. What to do if you still can’t connect
If it still fails after switching networks, try the following: update v2rayNG to the latest version; delete nodes that clearly time out; import your subscription link again; check that the link wasn’t copied incompletely; and avoid running other VPNs, accelerators, or proxy tools at the same time. If the log shows a certificate, transport, or reality-related error, the node parameters are probably mismatched, so try another node or refresh your subscription.
In short, don’t start by randomly changing advanced v2rayNG settings. Follow this order: “time and permissions—nodes and subscription—client settings—switch network environments—check the log.” This will usually help you identify the problem faster and avoid breaking a configuration that was working.