Oct 23, 2026 · Troubleshooting · About 8 min read

V2Ray Connected but Websites Won’t Load: A Troubleshooting Checklist for System Proxy, Routing, and DNS

Your client says it’s connected, but the browser keeps loading. Check the local proxy port, system proxy, routing rules, DNS, and clock in order to find where traffic stops.

At a glance

For users whose v2rayN is running or whose v2rayNG shows the VPN icon, but websites still time out. A connected status doesn’t mean your browser is using the proxy—or that the server can reach the site. Test the same URL and change one setting at a time to find whether the request is stopping at the local listener, routing, DNS, or the outbound handshake.

1. Check that the local proxy port is listening

In v2rayN for Windows, open Settings → Parameter Settings and check the local listening port and inbound type. Depending on the version, HTTP and SOCKS may use separate ports, or both may use a mixed port. The numbers below are examples for testing; use the values shown in the app and core logs. Android’s VPN mode doesn’t require you to enter these ports in your browser.

127.0.0.1
IPv4 loopback address
10808
Example local SOCKS port
10809
Example port for a separate HTTP inbound

Run these two commands in PowerShell. If the SOCKS port shown in the app isn’t 10808, replace that number in the commands first. The first command tests a local TCP connection; the second sends an HTTPS request through SOCKS and lets the proxy resolve the destination hostname.

Test-NetConnection 127.0.0.1 -Port 10808
curl.exe -v --max-time 15 --proxy socks5h://127.0.0.1:10808 https://example.com/

What the results mean: choose your next step

If TcpTestSucceeded : False, check the port and core process first—not DNS. A successful TCP test only means a process accepted the connection. If the second command returns an HTTP response but the same URL times out in your browser, check whether the browser is using the proxy.

2. Make sure browser traffic is going through the proxy

Note your current settings before testing. On Windows, don’t switch to TUN while troubleshooting the system proxy. On Android, don’t switch between Wi-Fi and mobile data while checking the VPN. Otherwise, even if the page loads again, you won’t know which change fixed it.

  1. Check the tray menu mode

    Right-click the v2rayN tray icon and select “Set system proxy automatically.” If the menu currently says “Clear system proxy,” the core may be running normally, but browsers that rely on the system proxy won’t be routed through it. Restore the original mode after testing.

  2. Check the system proxy address

    Open Windows Settings → Network & internet → Proxy and check that the manual proxy address and port match the HTTP or mixed inbound provided by the client. Don’t enter a SOCKS-only port as an HTTP proxy, and don’t overwrite proxy settings managed by your organization.

  3. Check which apps are included

    In v2rayNG, open Settings → Per-app proxy. If it’s enabled, check whether your browser is included or excluded; the list’s meaning depends on the selected mode. You can temporarily disable per-app proxy, disconnect and reconnect, then retry in the same browser. Restore your original app list afterward.

  4. Rule out stale browser settings

    Reopen the browser and try the same URL. Check the browser’s own proxy settings and extensions, too. If another browser works, that only confirms one app’s traffic path is working; it doesn’t mean every app uses the same proxy or DNS.

3. Check whether a routing rule selects the wrong outbound

Routing decides whether traffic goes direct, through a proxy, or gets blocked after it reaches the core. In v2rayN, check the selected profile under “Routing” in the tray menu; in v2rayNG, check “Routing settings” under “Settings.” Menu locations may vary by version. Note the current profile, reproduce the problem, then check the core logs for the destination and outbound tag. Tag names depend on your configuration.

4. Tell local DNS resolution apart from proxy-side resolution

The server hostname and the website domain involve two separate DNS lookups. Even if the proxy resolves the destination website, your device or the core may still need to resolve the proxy server’s hostname first. Check the error log to identify which hostname failed, then determine which side is responsible for resolving it.

On Windows, compare these two requests through the same SOCKS inbound. With socks5, curl resolves the destination locally; socks5h sends the hostname to the proxy to resolve. This can also change whether the core sees the destination as an IP address or a hostname, so check the routing logs if the results differ.

Resolve-DnsName example.com
curl.exe -v --max-time 15 --proxy socks5://127.0.0.1:10808 https://example.com/
curl.exe -v --max-time 15 --proxy socks5h://127.0.0.1:10808 https://example.com/

Error: bind: address already in use

Cause: The local address and port the core is trying to bind are already in use. Fix: Use the port shown in the log to identify the process occupying it. Close any duplicate client instances, or switch to an unused port and update the proxy settings to match.

Error: Could not resolve host

Cause: curl couldn’t resolve the destination hostname locally. Fix: Check the spelling, then compare results using Resolve-DnsName. If the system lookup succeeds but only the browser reports a DNS error, check the browser’s Secure DNS settings.

Error: failed to find an available destination

Cause: This core error means the attempted outbound connection failed; by itself, it doesn’t indicate a DNS problem. Fix: Check the underlying error in the same log entry. If it says connection refused, verify the remote address and port instead of changing local DNS.

5. Check the clock and outbound handshake

If the local listener and DNS are working but the logs show a certificate validity error or handshake failure, correct the device clock first. VMess authentication requires the device clock to be accurate, and TLS uses the current time to check certificate validity. Changing the time zone won’t fix an incorrect clock; confirm the time actually synced.

Frequently asked questions

The server latency test succeeds. Why won’t websites load?

A successful test doesn’t mean your browser is using the same route. Open the same domain in your browser and with an explicit proxy command. If only the browser fails, check the system proxy, browser extensions, or v2rayNG’s per-app list.

Why does everything stop working when I turn on the proxy, but work again when I turn it off?

On Windows, start by testing the local port. If nothing is listening, enabling the system proxy just sends browser requests to an unavailable port. To get back online, select “Clear system proxy” from the tray menu, then check the core startup logs.

Should I re-import my subscription if switching networks fixes the problem?

Keep your current configuration and retry the same server and URL on both networks. If it fails only on a particular Wi-Fi network, check whether you need to sign in through a captive portal or whether an administrator has configured a proxy. Re-importing a subscription won’t fix a network access issue.

What information should I share when asking for help?

Include your operating system, client version, current mode, when the issue occurred, and the relevant error lines. Also say whether an explicit proxy test succeeded. Before sharing, redact subscription links, server credentials, and internal addresses; don’t upload your full configuration.

Client Downloads