How to Read v2rayN Logs: Common Errors and How to Troubleshoot Them

Learn how to set log levels and diagnose common v2rayN errors, including connection refused, i/o timeout, and TLS handshake failures.

At a glance

For Windows v2rayN users troubleshooting kernel startup failures or browser timeouts. Reproduce the issue with a single request, then use the logs to determine whether it points to the local listener, node connection, DNS resolution, or TLS verification. Change one setting at a time and repeat the same request to check whether it helped.

Set the log level and reproduce the issue once

Messages in v2rayN may come from the client or the running core. Subscription downloads, configuration generation, and core traffic forwarding are separate stages: a timeout while updating a subscription does not mean an imported node cannot connect. The examples below use v2rayN 7.x with Xray on Windows. Options may be arranged differently across builds, so first confirm which core is running and whether the log level applies.

  1. Enable diagnostic logging

    Go to “Settings” → “Parameter Settings” → “Core: Basic Settings” and set “Log Level” to info temporarily. If the same page has a logging toggle, make sure it is enabled too. Save and check for new core startup messages. Switch to debug only if the existing logs do not provide enough detail.

  2. Keep test conditions consistent

    Keep the current node and routing mode unchanged, and note the time of the test. To troubleshoot the Windows system proxy, select “Set system proxy” from the tray menu, then use a browser configured to follow system proxy settings to open a URL that previously failed. If the issue occurred in TUN mode, reproduce it in that mode first; do not switch proxy entry points at the same time.

  3. Capture the first error

    Look in the main window’s message area for entries around the test time. Keep the startup result, then capture the first specific error for the request along with a few surrounding lines. Note the address, port, and operation involved; do not copy only the final retry failure.

  4. Restore the log level

    Restore the original log level after testing to avoid recording visited destinations over time. Before sharing logs, redact subscription URLs, user IDs, tokens, node addresses, and actual destination domains. Keep the port type and full error phrase so others can identify which part of the connection failed.

Local ports: confirm the request reaches the core

An open client window does not mean the local proxy is listening. Go to “Settings” → “Parameter Settings” and check “Local listening port,” then compare it with the address and port set in the Windows system proxy. The numbers below are examples for reading logs, not fixed settings for every machine.

127.0.0.1
IPv4 loopback address: the request is still on this machine
10808
Example local listening port: check Parameter Settings for the actual value
443
Example remote TLS port: check the node configuration for the actual value

Start with the address, then read the error

When you see connection refused, first note the address in the error. If it is 127.0.0.1:10808, check the local listener. If it is the node address and port, changing the Windows system proxy port will not fix a refusal from the remote end.

In PowerShell, you can check whether a port is listening locally. Replace 10808 in the command with the actual port. This check does not connect to a remote host.

Get-NetTCPConnection -State Listen -LocalPort 10808 |
  Select-Object LocalAddress, LocalPort, OwningProcess

Common errors: refusals, timeouts, and TLS verification

The same error phrase can appear at different stages. Use the operation and address near the error line to identify the cause. If you only see a top-level failure message, check the underlying error for the same request rather than switching protocols right away.

Error: bind: address already in use

Cause: The local port cannot be bound, often because another process or instance is already listening. Windows may also display its own socket error text.

Fix: Find the PID using the port and exit any duplicate instance you confirm is no longer needed, or choose an unused port and update any manually configured proxy entry to match.

Error: connection refused

Cause: The connection was actively refused. The destination may not be listening, or a device along the route may have rejected it.

Fix: For a local address, check which process is listening. For a node address, verify the imported port and ask the service operator to confirm that the corresponding inbound listener is active.

Error: i/o timeout

Cause: An operation exceeded its time limit. A timeout after dial tcp occurs at a different stage from a read tcp timeout after the connection is established.

Fix: For a connection timeout, check the node address and port. For a read timeout, keep the handshake and first read error, then compare with another known-working node on the same network.

Error: no such host

Cause: The current lookup path could not resolve a required hostname. It may be the node’s domain or the destination domain.

Fix: Note the name shown after lookup and check its spelling. Then distinguish between system DNS and the core’s DNS settings: successful system resolution does not guarantee that the resolver used by the core can resolve it.

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

Cause: Standard TLS certificate verification found that the certificate is not currently within its validity period. An incorrect system clock can trigger this error too.

Fix: In Windows, go to “Settings” → “Time & language” → “Date & time” and sync the clock. If the issue persists, ask the service operator to check the validity of the certificate and its chain.

Handshake and routing: a TCP connection does not guarantee a working website

A reachable node port only shows that the transport layer may be working. For a standard TLS node, the server name and certificate still need to be verified. Even after a successful handshake, check whether the request used the expected outbound route. Do not disable certificate verification just to remove an error, and do not apply standard TLS certificate troubleshooting directly to REALITY configurations.

  1. Check the security type first. Open the current node’s edit window and compare its transport and security type with the original configuration from a trusted source. For standard TLS, if the certificate’s valid names do not match the requested name, check the server name (SNI) and the domains covered by the certificate. A resolvable connection address is not necessarily the server name you should enter.
  2. Then check the actual outbound route. Find the routing or outbound entry for the same request in the logs. If the domain went direct, check the “Routing” rules selected in v2rayN and their matching order instead of repeatedly switching proxy nodes. accepted means only that the core received the request; it does not mean the destination website returned a response.
  3. Finally, compare results to narrow it down. If the same destination fails on two nodes, try another test destination. If only one domain fails, check DNS resolution and routing first. When switching networks without changing nodes, keep the test address the same and record the result so you do not mistake a network change for a settings fix.

Common questions about troubleshooting logs

Why does the speed test show a result when the browser still cannot open websites?

The speed test and browser may use different entry points and may not access the same destination. Note when you refresh the browser, confirm the core received that request, then check the outbound result. If there is no inbound entry, start by checking the system proxy and browser proxy settings.

The last line says no available destination was found. Which line should I check?

failed to find an available destination is often a summary of multiple failed attempts, not just a DNS resolution failure. Look earlier in the same request for lookup, dial, or a certificate error. If log entries overlap, close other test pages and reproduce the issue once.

Why can’t I see browser requests even with debug logging enabled?

First confirm the core started successfully after you changed the log level, then test with an app that clearly follows system proxy settings. If requests appear in system proxy mode but not in the original TUN mode, check each entry point’s settings separately. Do not treat their logs as one test.

What information should I include when sending logs to the service operator?

Record the full client version from v2rayN’s version information and the core name and version from the startup messages. Include the operating mode, time of reproduction, and the first specific error with sensitive details redacted. Report what happened when you changed networks with the same node and when you changed nodes on the same network. Mark comparisons you did not run as untested.

Download V2Ray clients