This article addresses the question “What should I do if v2rayNG won’t connect?” It focuses on low-risk troubleshooting steps ordinary users can try first, and when to switch between Wi‑Fi, mobile data, or a hotspot.
First, rule out basic configuration issues
Many connection failures aren’t caused by an inactive node, but by problems with importing settings, permissions, or the system’s network status. Check these in order rather than repeatedly deleting and reinstalling the app right away.
- Open v2rayNG and make sure the selected node isn’t an empty configuration. Check that the address, port, UUID, transport protocol, and other details have all been imported.
- If you use a subscription, open the subscription settings, tap Update subscription, and then select another node to test.
- Make sure your phone’s time is set to sync automatically. A significant time discrepancy can cause TLS handshakes to fail.
- Check that v2rayNG has VPN permission. When connecting for the first time, tap Allow in the system prompt.
- Close any other VPN, accelerator, or proxy apps to prevent multiple proxies from competing for the network.
If you’re using the free nodes provided on this site, try updating the subscription or testing another node in the same group, as free nodes may be temporarily congested or unavailable.
Low-risk troubleshooting: follow these steps in order
Without changing any complicated settings, try the following first:
- Switch nodes: Try 2–3 nodes from the same subscription instead of testing just one.
- Restart the connection: Tap Stop, then Start. If needed, clear the app from the background and reopen v2rayNG.
- Switch routing modes: If Global or Bypass LAN is enabled, temporarily switch to Global to see whether you can open web pages.
- Test different apps: If a browser won’t open, try another browser or test apps such as Telegram or YouTube to see whether the issue is limited to one app.
If you see errors such as timeout, connection refused, or TLS handshake failed, the cause is usually related to node status, network blocking, or protocol compatibility. If the VPN icon doesn’t appear at all, check system permissions first.
When to switch network environments
If you’ve confirmed that your subscription is working, multiple nodes won’t connect, and the service works for other users or on other devices, consider switching network environments. For example, switch from Wi‑Fi to mobile data, or from mobile data to home Wi‑Fi. You can also temporarily use another phone as a hotspot for testing.
Switching networks is especially recommended if your current Wi‑Fi requires authentication, such as campus, office, or hotel Wi‑Fi; the connection keeps timing out; the same node works on another network; or your carrier’s network has been experiencing recent issues. Switching networks is just a troubleshooting step and won’t change your node settings, so it’s a low-risk check.
What if it still won’t connect?
If it still fails after switching networks, delete the current configuration, reimport the subscription, and update to the latest version of v2rayNG. Don’t change settings such as the transport layer, security type, or camouflage domain unless the node provider explicitly instructs you to. As a last step, note the keywords in the error log and use the specific error to determine whether the cause is an inactive node, a DNS issue, or a client-version compatibility problem.
In short: If v2rayNG won’t connect, check the configuration and permissions first, then try another node and routing mode, and switch networks last. Following this order usually helps you find the cause faster and avoid accidentally deleting a working configuration.