What should you do if v2rayNG won’t connect? This guide helps you distinguish between local network issues, VPN permission conflicts, expired subscriptions, and unavailable nodes, with checks ordered from simplest to most complex. It’s intended for Android users who can’t access the internet after starting the app, get timeouts when testing a connection, or find that some apps can’t connect.
1. First, make sure your phone can connect to the internet
Stop v2rayNG and try opening a website you can normally access directly. If it still won’t load, troubleshoot your Wi-Fi, mobile data, or network login first rather than repeatedly changing nodes.
- Turn Wi-Fi or mobile data off and back on. Check for unpaid charges, data limits, or a weak signal.
- If you’re using public Wi-Fi at a hotel, school, or similar location, complete the web login first, then start the client.
- Test the same node over both Wi-Fi and mobile data. If it fails on only one network, check that network’s restrictions or router settings first.
- Set your phone’s date and time to update automatically. A large time discrepancy can cause TLS certificate verification to fail.
Change only one thing at a time and record the results. Avoid changing networks, nodes, and settings all at once, or you won’t know what caused the issue.
2. Check VPN permissions and the client’s status
When you start v2rayNG, allow the VPN connection request shown by Android. If the connection doesn’t start, check whether another VPN, network booster, or ad blocker that uses a local VPN is running. These apps generally can’t use the system VPN at the same time.
Close any conflicting apps and reconnect. If the connection drops only after you lock the screen, allow v2rayNG to run in the background in your system battery settings and disable battery-saving restrictions for it. If your client is outdated, update it through the project’s official release channels. Avoid modified versions from unknown sources.
3. Check whether the subscription and nodes are valid
- Update the subscription in subscription management, and check for download failures, empty content, or parsing errors. Menu names may vary by version.
- Make sure you’ve selected the node you want to use, rather than simply importing it. If the subscription won’t update, check that the link is complete and hasn’t expired.
- Test the current configuration, then try another available node for comparison. A latency value doesn’t guarantee that websites will open; test by actually visiting one.
- If the node came from a share link, copy and import the entire link again. Don’t change the address, port, UUID, TLS, or transport settings at random.
Free nodes may temporarily stop working or be subject to usage restrictions. If you’re using this site’s free nodes, check the update notes as well. A single failed node doesn’t mean there’s a problem with your phone or client.
4. Connected but can’t open websites? Here’s what to check next
First, check your routing and per-app proxy settings. If app filtering is enabled, make sure your browser hasn’t been excluded. You can temporarily disable per-app rules or switch to global proxy mode for comparison, then restore your original settings when you’re done.
If the logs repeatedly show domain resolution errors, temporarily set Android’s “Private DNS” to Automatic and try again. Also check whether you’ve changed the client’s DNS settings manually. Don’t enter several unfamiliar DNS addresses at once.
Open the client logs and check which step is failing: timeout usually indicates a connection timeout; connection refused may mean the remote port is unavailable; and a certificate error means you should check the system time and node settings. Log messages are clues for troubleshooting, not definitive conclusions.
When asking for help, include your network type, client version, the nodes you tested, and the error message. Before sharing screenshots, hide sensitive information such as subscription links and UUIDs. Don’t share your full configuration.