· Troubleshooting · 8 min read

How to Read V2Ray Logs: Common Errors and Troubleshooting Steps

Learn how to open client logs, adjust log levels, and diagnose handshake failures, connection timeouts, port conflicts, and clock issues—with a step-by-step troubleshooting workflow.

At a glance

This guide is for anyone dealing with a core startup failure, timeouts as soon as the proxy is enabled, or access problems limited to certain sites. Capture the log from one failed request, then check the local listener, routing rules, DNS resolution, remote connection, and protocol handshake—in that order. Change one setting at a time and retest the same URL so a temporary recovery isn't mistaken for a fix.

Open the client logs and capture a failure

Client logs and core logs answer different questions. Client logs show whether a subscription downloaded and a configuration loaded; core logs are better for diagnosing local ports, outbound connections, and handshakes. A successful subscription update only means the subscription URL was reachable at that moment—it doesn't mean every node in it is reachable.

  1. Open the logs

    On desktop, this example uses v2rayN 7.x: open the main window and check the information panel below the node list. On Android, open v2rayNG or v2flyNG, tap “☰” in the top-left corner, then select “Logs” (some builds show “Logcat”). Note the client version and the core version shown in the log's startup line. v2rayNG uses Xray, while v2flyNG uses the V2Fly core, so their error messages may differ.

  2. Set the log level to info

    In v2rayN, go to “Settings” → “Parameter settings,” open the Core basic settings, and find “Log level.” On Android, look under “☰” → “Settings” for the log level option. Menu names may vary by build. Start with info, save, and restart the connection; use debug briefly only if you need more context. If the option isn't available, troubleshoot with the logs you have.

  3. Reproduce the problem once

    Note when you tap Connect. After the core starts, use the same app to open the same failing URL once. Don't run a speed test, update the subscription, or switch nodes at the same time. If the error appears before you open a webpage, keep the startup logs; there's no need to send another request.

  4. Keep the surrounding log lines

    Copy about five lines before and after the failure. If the logs include connection IDs, follow only entries with the same ID so background app errors aren't confused with your test. Restore the previous log level when you're done. Before sharing logs, redact subscription URLs, account identifiers, node addresses, and visited domains.

Find where the request fails

App requestLocal listenerRouting matchOutbound connectionProtocol handshake

First check whether the request reached the core, then see which outbound it used. accepted in a log usually means only that the core received the request. If it then uses a direct outbound, you shouldn't expect to see a handshake with a node. If there's no request entry, first confirm that the current log level records connections, then check the system proxy, TUN, or Android app-routing scope.

Common log errors: messages, causes, and fixes

The entries below are searchable error snippets, not complete logs from a specific version. Prefixes and suffixes may vary by operating system, core version, and transport.

bind: address already in use

Cause: The address and port the core needs to listen on are already in use. Fix: Identify the process using the port, then close the duplicate instance or switch the client to a confirmed free port. Update any apps where you manually entered the proxy port.

connect: connection refused

Cause: The connection was explicitly refused, often because nothing is listening on the target port. Fix: If the target is 127.0.0.1, check that the core is running and the app has the correct port. If it's a node address, check the node port in your subscription and ask the provider to confirm the service is running.

i/o timeout

Cause: A network read, write, or connection attempt didn't finish in time. This message alone doesn't prove the node is unreachable. Fix: Check whether the same log line mentions lookup, dial tcp, or a read/write timeout. Keep the node unchanged and test again on a known-good network.

no such host

Cause: This DNS lookup didn't return a usable record. Fix: Identify the hostname that failed. If it's the node hostname, check its spelling against the subscription. If it's the website hostname, first determine whether the system, core, or remote server handles DNS, then check the corresponding DNS settings.

remote error: tls: handshake failure

Cause: The remote endpoint rejected the TLS handshake; this log line doesn't explain why. Fix: Compare the node port, transport, TLS setting, and server name against the subscription. If it still fails, give the provider the handshake time and redacted logs to investigate.

x509: certificate has expired or is not yet valid

Cause: According to the local system clock, the certificate is outside its validity period. The system time may be wrong, or the certificate may actually have expired. Fix: Sync the system clock first. If the error persists with the correct time, ask the provider to check the certificate. Don't disable certificate verification.

Check local ports and system time

Suppose the log shows the core trying to listen on 127.0.0.1:10808, but the bind fails. In Windows PowerShell, check which process is listening on that port. 10808 is only an example; replace it with the port shown in your log. If the error involves UDP, this TCP query can't rule out a port conflict.

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

In Task Manager, open the “Details” tab and find the process using the ID returned by OwningProcess. Don't end a process you don't recognize. If you decide to change ports—for example, to the confirmed free port 10818—save the change, restart the core, and check the proxy type and port configured in your apps. If HTTP and SOCKS use separate listeners, match each one correctly; a listening port doesn't mean the two protocols are interchangeable.

Choose a retest based on the scope of the problem

The log says the request was accepted. Why won't the site load?

Check the outbound tag for the same request. If it used a direct connection but you expected the proxy, check the current routing mode and the rule that matched. If it used the proxy, investigate the corresponding dial or handshake error. Retest the same URL without changing both the routing mode and node at once.

Only one node times out. Should I reinstall the client?

Don't reinstall yet. Keep the device, network, URL, and routing mode the same, and switch to a known-good node using the same protocol. If the comparison node works, check the failing node's address, port, and transport settings first. If both time out, investigate the current network and local configuration.

It works on desktop. Why are there no access logs after I tap Connect on my phone?

First confirm that Android has approved the client's VPN connection and that no other VPN is running. If per-app proxying is enabled, check whether the test browser is excluded or missing from the proxy-only list. Retest with the same node so app-routing issues aren't confused with node problems.

The error started right after a subscription update. Which logs should I check?

First look for an explicit subscription download or parsing error. If the update succeeded, make sure the newly updated node group is active, then disconnect, reconnect, and check the core startup lines. If the core starts but only the new node fails during the handshake, compare the transport and TLS settings before and after the update, one at a time. Don't restore all the old settings at once.

Client downloads