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

Learn how to read log levels and entries, diagnose common errors such as connection timeouts, handshake failures, port conflicts, and missing rule files, and follow a clear troubleshooting sequence.

At a glance

For v2rayN users dealing with a failed core startup, timed-out node tests, or an unresponsive browser. First check whether the local listener is up, then troubleshoot in order: name resolution, remote connection, handshake, and routing. Run one test and change one setting at a time, using the same request to verify each change.

Log Levels and Entry Format

Messages in the v2rayN interface and core logs come from different layers. A message saying the core is starting only means the client attempted to launch it; the core may still exit if its configuration fails to parse. A subscription update failure can occur while the client is fetching the subscription, so it should not automatically be treated as a handshake error with the current node.

ClueHow to read it
Timestamp and request IDFind the log entries that match the test time. If a request ID is present, follow that ID first to avoid mixing in background requests.
error / warningCheck for failures and exceptions. A warning does not necessarily mean the core has exited; check whether it continues listening or handling requests afterward.
info / debugUse this to see more processing details. Enable it briefly to capture the issue, then restore the previous level to avoid accumulating large volumes of access logs.
acceptedThese entries in the access log mean the core received a request; they do not confirm that a response came back from the remote server.

The > in an error chain often links an outer operation to the underlying cause. Don’t stop at “connection failed”; look for a later lookup, dial tcp, x509, or file path. Multiple components may report the same error, so focus on the part that names a specific address, port, or file.

Capture Logs for a Single Request

  1. Record the Current Configuration

    Note the selected node, active core, system proxy status, and TUN status. On desktop, check the local listener options under Settings → Parameters. Menu names can vary by version, so use the port shown on the configuration page and in the startup log as your reference.

  2. Check the Log Level

    Under Settings → Parameters, check which logging options are available in your version. If a core log level is available, temporarily select info. For a custom Xray configuration, the relevant field is log.loglevel. Don’t directly edit a configuration that the client regenerates on the next launch.

  3. Send One Request

    Once you’ve confirmed the core is still running, open a known-good test page in your browser and note the time. Pause batch latency tests to avoid generating multiple connections at once. If the issue occurs only during subscription updates, run one update without testing a webpage at the same time.

  4. Find the First Cause

    Keep the startup entry, the failure entry, and the surrounding error chain. Before sharing logs, redact subscription and node addresses, identity fields, and requested destinations; retain the error keywords, port type, and event order. Repeat the same operation after making a change to confirm the original error is gone and the request succeeds.

Port Conflicts and Local Proxy Listeners

127.0.0.1
IPv4 loopback address
10808
Example local listening port
443
Example remote TLS port

Check the address in the error, not just the port number

If the log says listen tcp 127.0.0.1:10808, first check which process is listening on your machine. If it says dial tcp followed by a remote address, check the node’s port and connectivity. Changing the local proxy port won’t fix a remote connection problem.

Use Windows PowerShell to find the process listening on a specific port. The port below is only an example; replace it with the local port shown in your log before running the command.

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

In Task Manager, open the Details tab and match the PID to the process. If it’s a duplicate client instance, close the extra instance normally. If the port belongs to an application you still need, choose an unused port in v2rayN and update any apps where you entered the proxy address manually. After restarting the core, confirm that the new port is listening and that the app uses the same port and the correct proxy type.

Connection Timeouts, Handshake Failures, and Missing Rule Files

The keywords below can appear in different parts of a full error chain, and their prefixes and punctuation vary by core and platform. First identify which operation the error describes; then consider changing the configuration.

Error: i/o timeout

Cause: A read, write, or connection attempt timed out. This message alone doesn’t pinpoint the problem.

Fix: If the preceding entry contains dial tcp, check the remote address and port first. If it contains lookup, check name resolution and the DNS path.

Error: connection refused

Cause: The connection was refused, often because nothing is listening on the target port, though an intermediary device may also have actively rejected it.

Fix: First determine whether the target is a loopback or node address. Then check the local listener, or ask your service provider to verify the remote service port.

Error: x509: certificate signed by unknown authority

Cause: The TLS client can’t verify the peer’s certificate chain back to a trusted root certificate.

Fix: Confirm you’re connecting to the intended service and ask its administrator to check the certificate chain. For internal certificates, configure trust using your administrator’s instructions; don’t disable certificate verification.

Error: address already in use

Cause: The local address and port being bound are already in use by another listener.

Fix: Find the process using the port shown in the error and close any confirmed duplicate instances, or change the local inbound port and update the app’s proxy settings.

Error: failed to load geoip

Cause: The core couldn’t load the IP rule data referenced by the configuration. The file may not be accessible, or the requested category may not exist in the data.

Fix: Check the path and category named in the underlying error. If the system says the file can’t be found, check the actual resource directory and restore the data file required by the rules. If the category is missing, check the rule reference.

geoip.dat provides IP classifications; geosite.dat provides domain classifications. Custom configurations may reference other data files as well. A file with the expected name in the client directory doesn’t prove the running core reads from there; use the path in the error chain. If the log reports a permissions error, check whether the account running the core can read the file instead of downloading it again. If the core exits while loading rules, fix the startup problem before testing a node.

If TCP connects but the TLS handshake fails, check that the transport security type and serverName in the node configuration match the server’s requirements. For certificate validity errors, also check the system date and time synchronization. An open port only confirms that TCP can connect; it doesn’t prove that TLS, node authentication, or the application request succeeds. Don’t substitute a port probe for an actual access test.

Common Log Questions

Why does the webpage still fail when the node test shows latency?

First confirm that the node used for the test is the active node. Then open a webpage and look for a core access log entry at the same time. If there is one, check routing and outbound errors. If there isn’t, confirm that access logging is enabled, then check whether the browser follows the system proxy or still has an old manual proxy port configured.

If timeouts happen only during subscription updates, should I check the node?

First identify whether the timeout belongs to the subscription request or the node connection. Note the time of a single manual update, then check the address in the subscription group, the connection method selected for the update, and whether that method currently works. If your existing nodes still work, don’t delete the entire subscription group just to fix updates.

The log shows accepted. How can I tell if the wrong outbound was used?

Check the outbound tag shown later in the same request. If the current log doesn’t show a tag, temporarily increase the log level. Compare the rule order in the active configuration and check whether routing.rules uses outboundTag to reference the expected outbounds tag. An accepted entry alone doesn’t tell you which route was taken.

If the problem only happens with TUN enabled, which log entry should I check?

Save the failure logs first, then turn off TUN and use the same node to test the same page through the system proxy. If the issue occurs only with TUN, check the earliest virtual adapter, permission, routing, or DNS error after enabling it. First determine whether the virtual adapter failed to start or started but isn’t forwarding requests correctly; then investigate the relevant setting.

Download v2rayNWindows / macOS / Android / Linux