v2rayN Connection Timeout: Troubleshooting from Your PC to the Server

Troubleshoot v2rayN connection timeouts step by step: check your system clock, local ports, Windows proxy settings, subscription details, transport settings, and TLS. Includes checks for each step.

At a glance

If a node times out, don't start changing settings in bulk. On Windows, first sync the clock and confirm the core is listening on a local port. Then check whether your apps use the system proxy. Once those are working, verify the subscription entry, remote port, and handshake settings. Change one thing at a time and retest the same node against the same destination to see what made a difference.

1. Sync your clock and check the local port

After waking from sleep, restoring a VM snapshot, or reinstalling Windows, check the system clock first. An incorrect clock can make TLS certificates appear not yet valid or expired. Next, confirm the core has started and is listening. If the local listener isn't running, browser traffic hasn't reached the node yet, so changing the remote address won't help.

10808
Example local inbound port; use the value in your client settings
443
Example remote TLS port; use the value in the node entry
  1. Sync your clock

    Open Windows Settings → Time & language → Date & time. Check your time zone, turn on Set time automatically, then select Sync now under Additional settings. If syncing fails, fix the local clock first. If the time is correct but the certificate still appears expired, ask the administrator to check the server certificate.

  2. Find the inbound port

    In v2rayN, open Settings → Parameter settings and look for Local listening port or the inbound settings. Names vary by version; you can also check the core startup log for the port it actually listens on. Don't enter the remote port from the node editor here.

  3. Check which process owns the listener

    Select and enable the node, then use PowerShell to check the local listener. Replace 10808 below with the actual port. Use OwningProcess from the output to check the PID on Task Manager's Details tab. If it's the current core, the listener is expected. If it's a different program you've identified, close it normally or give v2rayN an unused port. Restart the core and confirm the system proxy points to the right local endpoint.

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

If no listener appears, find the first startup error in the log and check whether the core loaded its configuration successfully. No listener doesn't automatically mean a port conflict. Change the port only if the startup error reports a bind failure and you've identified what owns it. Don't terminate an unfamiliar process based on its PID alone.

2. Distinguish node tests from system proxy traffic

App requestLocal inboundRouting ruleNode outboundDestination

The node list's real connection test and browsing are not the same traffic path. The client initiates the connection test. Browser traffic also depends on whether the browser uses the Windows system proxy and whether routing rules send the request through the proxy outbound. A successful TCP latency test only confirms a connection to the remote port; it doesn't verify access to a destination through the node.

  • Real connection test succeeds, but the browser fails: In v2rayN's system tray menu, select System proxy → Set system proxy (wording varies by version). Then open Windows Settings → Network & Internet → Proxy and check that the manual proxy address and port match the client settings. If the browser has its own proxy settings, make sure they aren't overriding the system settings.
  • The browser works, but a specific app fails: Check whether the app reads the system proxy or needs its own proxy settings. Don't switch the system proxy, routing rules, and TUN all at once just to test browser access. Even if that fixes things, you won't know which layer was responsible.
  • Several nodes time out: Repeat the real connection test with the same nodes, then check whether the test destination is reachable. A failure to reach one test destination doesn't prove that every node is down. Try another destination you know is reachable and compare the core logs before drawing conclusions.

3. Check the subscription update and active node

A subscription URL retrieves a list of nodes; it isn't a node's connection address. If an update fails, the list may still contain nodes from the last import. Even a successful update doesn't mean the new entry is active. Nodes with the same name may have different server addresses, ports, or transport settings.

  1. In the main window, select the affected subscription group, then use the Subscription group menu to update it and check the update log. If the menu offers update through proxy and update without proxy, try the first option if you have another stable, working node. If every node is failing, don't rely on a broken node to fetch new settings.
  2. After updating, double-click the new entry and check its protocol, server address, port, transport, and TLS fields. Follow the subscription provider's latest instructions; don't piece together settings from another node that only looks similar. Don't manually change a VMess entry to VLESS: the client and server must use the same protocol.
  3. Right-click the node you just checked and set it as the active server, then run the real connection test again. If the log still shows the old address, check that you didn't select an older entry with the same name and that the core has applied the updated configuration.

4. Check remote connectivity, then verify transport and TLS

For nodes that use TCP, run Test-NetConnection -ComputerName in Windows PowerShell to check the node address, and use -Port to specify the node port. This tests TCP connectivity from your PC to the remote port directly; it doesn't go through v2rayN's HTTP or SOCKS inbound. Only test node addresses you manage or that your provider assigned to you.

ResultNext step
Node hostname couldn't be resolvedCheck for extra spaces or a subscription URL entered by mistake. Confirm the DNS results match the records provided by your service provider.
TcpTestSucceeded is FalseCheck the remote address and port first. For a server you manage, check its listener, firewall, and cloud security group. For a hosted node, send the failure time and node name to your provider.
TcpTestSucceeded is True, but proxy requests still failTCP connected, but that doesn't confirm TLS, the transport protocol, or authentication is working. Compare the settings below and check the handshake logs.
  • Transport: For WebSocket, check the path and Host. For gRPC, check the service name. If the client path doesn't match the server or reverse proxy endpoint, proxy requests may fail even when the port is reachable.
  • TLS: Check the security setting and server name (SNI). The connection address, certificate name, and WebSocket Host may differ; use the values specified in the server configuration. If the name doesn't match or the certificate is expired, don't enable Allow insecure as a fix.
  • REALITY: If the subscription explicitly uses REALITY, check the server name, public key, and Short ID against the provider's latest node entry, and confirm the current core supports the settings. Don't replace these values with fields from a regular TLS node.

5. Find the failure point in the logs

A clear record of one failed attempt is more useful than repeatedly running speed tests. Note the time, leave just one node active, and look for errors mentioning the destination near that request. The top-level message may combine several retries into one line; the specific cause is often in the nested error on the same log entry.

Error: bind: address already in use

Cause: The local address and port the core is trying to listen on are already in use. Fix: Check which process owns the port shown in the log. Once you've confirmed what it is, close the duplicate instance or change the local port.

Error: i/o timeout

Cause: A network operation exceeded its timeout. This message alone doesn't tell you whether the connection attempt or a read/write operation timed out. Fix: Check whether it follows dial tcp or read tcp. For the former, test the remote port first. For the latter, use nearby transport, handshake, and destination request logs to narrow it down.

Error: remote error: tls: handshake failure

Cause: The remote server reported a TLS handshake failure, but the error doesn't identify which setting is mismatched. Fix: Check the port, security type, and server name first. For a server you manage, check the server or reverse proxy logs at the same time.

Error: failed to find an available destination

Cause: The outbound connection couldn't find an available destination. This is a summary message, not necessarily a DNS issue. Fix: Read the nested error in the same log entry. If it says no such host, check DNS. If it says connection refused, check the destination address and port, and whether anything is listening on that port.

6. How to interpret common retest results

Only one node in the subscription fails. Should I reinstall?

Not yet. Leave your local settings unchanged and test another node in the same group against the same destination. If it works, update the subscription and check the failing node's address, port, and transport settings. If it still fails, send the node's error to your provider.

It connects over my phone's hotspot. What's the problem?

Test both networks on the same PC, using the same node and destination. If only the original network fails, compare DNS results and remote TCP connectivity on both networks, then check whether the original network requires a sign-in portal or centrally managed proxy settings. This comparison shows the issue is related to the network environment, but one speed test can't identify the exact cause.

Only one website won't open. Should I still check the server?

If other sites work through the same node, first check whether the failing domain is routed directly or through the proxy, then review its DNS results and request logs. If the node can proxy other requests, don't start by changing shared TLS or subscription settings.

View downloads