V2Ray Connected but No Internet? Troubleshoot System Proxy, DNS, and More

Check system proxy settings, local ports, node details and system time, routing rules, DNS, and TUN conflicts to find out why V2Ray connects but websites won't load.

At a glance

For users whose v2rayN or v2rayNG shows as running while the browser times out. Choose a reproducible HTTPS URL, confirm the request reaches the client, then use the logs to check the node handshake, routing, and DNS resolution. On desktop, finish by testing TUN on its own.

First, confirm the system proxy is receiving browser requests

A tray icon or Android VPN indicator means the local service is running; it doesn't confirm that the destination website is reachable. Note the URL, browser error, and time of failure. Change one setting at a time and retest the same URL so changes to the network, node, and routing don't muddy the results.

  1. Check the underlying network

    On desktop, turn off TUN first, then select “Clear system proxy” from the v2rayN tray menu under “System proxy.” Try a site known to be directly reachable. If that won't load either, check whether Wi-Fi requires a captive portal sign-in or the device still has a manual proxy configured.

  2. Check the proxy address

    From the tray menu, select “Set system proxy.” In Windows 11, go to Settings → Network & internet → Proxy and check the address and port under “Manual proxy setup.” Make sure they point to v2rayN's local HTTP or mixed inbound.

  3. Retest the same page

    Open a new browser window, retry the URL, and check the v2rayN logs. If access logging is enabled but there's no matching request, check for a browser-specific proxy, proxy extension, or bypass rule. Don't assume all desktop apps follow the system proxy based on browser results alone.

Check the local listening port and proxy type

127.0.0.1
Local IPv4 loopback address
10808
Example port for the mixed inbound in this section
443
Default port for the destination HTTPS service

Check the local port in v2rayN under Settings → Parameter settings, and use the current configuration and startup logs as the source of truth. Some versions provide a mixed inbound; others configure HTTP and SOCKS separately. Don't enter a SOCKS-only port as the Windows manual HTTP proxy, or confuse the node's port with the local listening port.

The examples below use Windows PowerShell and assume the HTTP or mixed inbound is listening on 127.0.0.1:10808. If your port differs, replace both example values.

Get-NetTCPConnection -LocalPort 10808 -State Listen
curl.exe --verbose --max-time 15 --proxy http://127.0.0.1:10808 https://example.com/

What it means: explicit proxy works, so check the app's proxy settings first

If the same URL loads through an explicitly configured proxy but not in the browser, check the browser's proxy settings and bypass rules before changing node details. This only confirms that this request succeeded; it doesn't prove other domains use the same outbound.

Use the logs to check node settings and system time

Once the client receives the request, check the selected node. Double-click it in v2rayN to open its settings, then compare each field with the configuration from your server or provider: address, port, protocol, user ID, transport, and security. For VLESS with Vision, also check flow. For REALITY, check the server name, public key, and Short ID. Don't hide TLS errors by disabling certificate verification.

Error: bind: address already in use

Cause: The local address and port are already in use, so the new inbound can't bind to them. Fix: Identify the process using the port, exit any duplicate client instances normally, or switch to an unused port and update the system proxy to match.

Error: failed to find an available destination

Cause: No usable destination was found for the outbound attempt. This outer-level message alone doesn't prove that DNS failed. Fix: Read the inner details in the same error chain to distinguish a hostname lookup failure from a refused connection or timeout.

Error: x509: certificate has expired or is not yet valid

Cause: The current time falls outside the certificate's validity period. The device clock may be wrong, or there may be a server certificate issue. Fix: In Windows, go to Settings → Time & language → Date & time and select “Sync now,” then retry. If the time is correct and the error persists, ask the server administrator to check the certificate.

VMess authentication also depends on the client and server clocks being in sync. If the system time is correct but the connection still fails, check the server time and user configuration. When sharing logs, include the full error chain and test time, but remove subscription URLs, user IDs, and other credentials.

Tell routing issues apart from DNS failures

If only certain websites fail, check the request's destination and outbound tag in the access log; tag names depend on the current configuration. A request that reaches the client but is sent to a direct or blocked outbound is different from one that never reaches the client.

Test TUN and Android VPN routing separately

If the system proxy works but TUN doesn't, clear the system proxy, enable TUN alone, and confirm that the virtual network adapter was created. Retest the same website, then check whether the interface routes or DNS changed. Running both modes at once doesn't always cause a conflict, but it makes the failure path harder to trace.

TUN blocks access to your local network too?

Turn off TUN first and confirm that the same local network address is reachable again. On Windows, run route print before and after toggling TUN, then compare the interface and route for the target subnet. Check whether TUN has taken over that subnet; configure a direct route or exclusion as needed, without deleting system routes.

Android shows a VPN icon, but one app won't connect?

In v2rayNG, check “Per-app proxy” and the app list under Settings. Confirm whether only listed apps are proxied or listed apps are bypassed. Reconnect and retest after making changes. Also check whether Android's “Always-on VPN” is assigned to another app; menu locations vary by Android version.

Browser still offline after you exit the client?

Go back to the system proxy settings and check whether a manual proxy still points to a local port that is no longer listening. Clear it only if you confirm the client set that value. If it's a work- or school-managed proxy, restore the original setting or contact your administrator.

Download clients