Node HandbookNODE HANDBOOK中文
v2rayN · Windows

v2rayN shows a node and a latency value, but pages do not load

Three states get mixed together here: whether the target node is actually the active server, whether the core started without an error, and whether Windows is using the local port the client opened. Check them in that order before updating the subscription again.

Node Handbook editorial team ·

A two-minute triage

  • Open the v2rayN log and confirm there is no core-start failure, config parse failure or port-in-use error.
  • Select the node and set it as the active server — do not stop at seeing it in the list.
  • Turn TUN off and test one ordinary HTTPS site using the system proxy only.
  • If the system proxy works and TUN does not, keep that contrast and move to the TUN path; do not also rewrite the subscription in the same round.
  • If the system proxy also fails, check the listening port, node reachability and the core log.
  • If only individual sites fail, record the domain, the error text and the matched rule. Do not reset the whole client.

What “connected” can mean on its own

A selected node, a latency value or a successful subscription update each prove one step finished. None of them individually proves that:

  • the node is the active server;
  • the core (Xray, sing-box or another) started without an error;
  • the local port v2rayN uses for the Windows system proxy is listening;
  • Windows is pointing at that port;
  • DNS requests take a working path;
  • the TUN adapter, routes and firewall allow traffic through.

That is why the order is log and port first, browser second. Repeatedly clicking “test latency” produces numbers without answering any of the six questions.

Step 1: confirm the core actually started

Open the log and restart the service, then find the entries for this start. A field validation failure, a missing core binary, an architecture mismatch or a port already in use all have to be resolved first. A normal-looking interface does not mean a normal core: with no core running, the system proxy can still point at 127.0.0.1, and the browser then reports a proxy connection failure.

Safe recovery when that happens: clear the system proxy, turn TUN off, quit v2rayN, verify Windows no longer holds a stale 127.0.0.1:port value, and confirm ordinary networking before working on the core error. Do not delete the whole configuration directory while you are still unsure what it contains.

Step 2: active server and local port

Set the target node as the active server, then find the local port the client uses for the system proxy in the status bar or settings. Do not substitute a SOCKS port for an HTTP or mixed port, and do not assume every version shares the same default.

Once the interface shows the port, confirm a local process is listening on it. In PowerShell, with 10808 replaced by your actual value:

Get-NetTCPConnection -State Listen -LocalPort 10808

Read OwningProcess from the result, then check that PID:

Get-Process -Id 1234

This establishes which process listens on that port. It does not establish that the port type suits the current proxy setting, nor that the node can reach a website. Microsoft documents -LocalPort and -State Listen for Get-NetTCPConnection, and PID-based lookup for Get-Process.

If Clash, Hiddify, another v2rayN instance or a browser proxy extension is also running, a port conflict or a second capture layer is possible. Keep one proxy client active, restart the v2rayN service, and retest. Do not enable TUN in two programs at once.

Step 3: test the system proxy on its own

With TUN off, enable the client's system-proxy option and test in the browser. If the log records no browser request at all, treat that as a clue rather than a conclusion: check the log level and time range, whether Windows still points at an old port, whether the browser uses its own proxy extension, and whether security software blocks loopback connections.

If ordinary pages stop loading the moment v2rayN quits, clear the system proxy. Continuing to switch nodes while Windows points at 127.0.0.1:port with nothing listening changes nothing that matters.

Step 4: when the error mentions DNS, stop expanding the change set

DNS_PROBE_FINISHED_NXDOMAIN, resolution timeouts and DoH request timeouts in the log are a different class of failure from “nothing is listening on the local port”. Record the exact error, the time, the core in use and the mode, then make single-variable comparisons against a second resolver. Do not disable certificate verification to get past it, and do not upload a private subscription to a public converter or diagnostic site.

Step 5: system proxy works, TUN does not

Do not touch the subscription here. Record the conclusion — same node, same core, system proxy works, TUN fails — then compare capture behaviour. If the change followed an upgrade, keep a configuration backup plus the client and core versions, and check the official releases and issue records for that combination. An issue record shows that a similar symptom occurred in a specific environment; it does not prove your cause is identical. Do not replace official release binaries with third-party repacks.

Step 6: one site fails, not the client

If most sites work and one domain fails, that establishes only that some traffic currently works. Record the browser error, the log hit and the routing decision. If you use direct connection as a control, the site sees your real local exit — do not bypass the proxy casually for privacy-sensitive or account-bound services.

Minimum recovery order

  1. Clear the system proxy in v2rayN.
  2. Turn TUN off.
  3. Quit v2rayN.
  4. Confirm Windows holds no stale 127.0.0.1 proxy value.
  5. Reconnect the network and test an ordinary site.
  6. Only after plain networking returns, enable the system proxy alone and retest one variable.

“Reset network” is not step one: it changes several variables simultaneously and can affect other networking software.

What to send to a provider or maintainer

  • OS build, v2rayN version, core and core version.
  • Mode in use: system proxy or TUN.
  • Time with time zone and the exact first error text.
  • Masked log excerpt, plus the contrast result (system proxy works / TUN fails).
  • Which process owns the local port, if you checked.

Mask the subscription URL, token, UUID, password, QR code and account identifiers. A connection report never needs a live credential.

Scope

This page covers Windows v2rayN. Button names and status-bar layout change between releases. The layering — core, active server, local port, system proxy, DNS, TUN — is what stays stable, and each layer should be changed one at a time with the ability to restore plain networking kept intact.