"It says connected but the browser won't load," "subscription keeps spinning," "every speed test times out," "it's painfully slow at night"—these are the most common V2Ray complaints. This handbook walks through prioritized checks that work for v2rayN (desktop) and v2rayNG / v2flyNG (Android). Don't skip steps: many issues are fixed in the first three.

Before you dig in: is it the client, or the node?

This is the most important split.

  • Client issues: proxy mode off, missing permissions, wrong APK ABI, outdated app, incorrect system time, and similar.
  • Node / subscription issues: expired plan, data quota used up, blocked routes, provider maintenance, or a single bad node.

If real connectivity tests fail across the board, suspect the subscription or nodes first. If tests look fine but web pages don't load, check system proxy / VPN permission and routing rules.

Standard troubleshooting flow (do these in order)

Step 1: Update the subscription

Node details change. Update the subscription before anything else. If the update fails, connect with any working node and retry, or check whether the subscription has expired. Desktop and Android clients can update subscriptions through a proxy (directly or via a workaround).

Step 2: Run a real connectivity test—don't trust fake latency bars

Some UIs show ICMP or other pseudo-latency that isn't very useful. Use the "real connection latency test." Pick low, stable nodes and skip ones that keep timing out. If only a few nodes work, the client is fine—route quality varies.

Step 3: Confirm traffic is actually going through the proxy

  • v2rayN: In the tray menu, is System Proxy set to auto-configure? Turn on TUN only when you need system-wide capture.
  • v2rayNG / v2flyNG: Is the bottom connect switch on? Did you approve the system VPN prompt? Is battery optimization killing the app?

Step 4: Sync system time

Large clock skew breaks TLS and some protocol handshakes. On phones and PCs, enable automatic date, time, and time zone.

Step 5: Upgrade the client (and core)

REALITY, Hysteria2, and new transports keep shipping. Older clients often update subscriptions fine but can't use new nodes. Get the latest builds from the download center.

Scenario A: Subscription update fails or spins forever

  1. Check that the URL is complete, with no extra spaces.
  2. Open the subscription URL in a browser to see if it loads (note: some feeds block browser user-agents).
  3. Connect with a backup node first, then update the subscription.
  4. Confirm the plan hasn't expired and you still have data left.
  5. Switch networks (Wi-Fi ↔ mobile data) to rule out a local firewall.

Scenario B: Every speed test times out

A total wipeout usually isn't "one bad node"—the upstream is down or the local network is heavily filtering. Try this order:

  • Log into the provider panel and check service status.
  • Retest on another network (for example, a phone hotspot).
  • Confirm your client version supports the protocols those nodes use.
  • If you just changed DNS or stacked multiple proxies, reset to defaults and retest.

Scenario C: Shows connected, but pages won't load

  • Desktop: Confirm system proxy is on; check for conflicting browser proxy extensions.
  • Android: Make sure another VPN isn't holding the tunnel; check whether per-app proxy excluded the browser.
  • Try disabling IPv6 (IPv6 leaks or network issues can cause partial connectivity).
  • Test with another browser or system component to rule out cache and extension interference.

Scenario D: Connected but very slow

Slow does not necessarily mean broken. Start with these steps:

  1. Run a real connection speed test and choose another node; do not cling to a familiar name.
  2. Avoid congested routes during peak hours and try nodes in less popular regions.
  3. Check for double proxying (system proxy + browser extension + layered rules).
  4. On desktop, compare the real-world experience of system proxy and TUN; one mode may be more stable.
  5. Check whether the device is thermal throttling or running many downloads at once.

Scenario E: Android crashes or disconnects immediately

  • Confirm that the APK architecture matches your device (prefer arm64-v8a).
  • Disable battery optimization and allow background activity.
  • Reinstall the latest version, then restore a backup or add the subscription again.
  • Check whether security software is blocking VPN creation.

Scenario F: macOS / Windows-specific issues

  • macOS says the app is damaged: remove the quarantine attribute with xattr -cr, then open it again.
  • Windows Defender false positive: add an exclusion; do not replace it with an installer from an unknown source.
  • A work PC may have enforced proxy or firewall policies that conflict with the client; test on another network.

How to read logs: focus on the essentials

You do not need to understand every line. Search for these first:

  • timeout / i/o timeout: the remote host cannot be reached or is blocked.
  • rejected / auth: bad configuration, incorrect UUID, or protocol mismatch.
  • TLS / certificate: a certificate, time, SNI, or REALITY parameter issue.

Matching key log messages against node parameters is more effective than repeatedly reinstalling the client.

Prevention: reduce future problems

  • Enable automatic subscription updates.
  • Keep at least two providers or subscriptions to avoid a single point of failure.
  • Keep your client updated from this site instead of using an outdated version for a year.
  • Record your minimum working configuration: which node and mode are most stable, so you can return to it.

Summary

V2Ray troubleshooting is not guesswork; it is a sequence: update the subscription → run a real connection speed test → confirm proxy/VPN is enabled → sync the time → update the client → check logs. Follow this chain and you can pinpoint the cause of 90% of "won't connect / very slow" problems. If your client is outdated, download and update it from this site first, then return to this guide and troubleshoot step by step.