v2rayN Port Already in Use: Find the Conflicting Process and Change the Listening Port

First, confirm it’s a bind error—not a node timeout

A local listening port is where apps such as browsers and terminals send traffic to the core. It is not the remote server port used by a node. If the log shows bind, listen tcp, or “address already in use” during core startup, troubleshoot the local listener first. Changing your subscription or VMess or VLESS node settings usually won’t resolve a port conflict.

In the v2rayN main window, open the log and keep the full output from core startup through the failure. A wrapper message may say “startup failed,” but look for the innermost error line: it typically identifies the protocol, IP address, port, and system error. The snippets below are examples; the exact log may vary by version.

Check the ports and version

Don’t assume there’s a conflict based only on port numbers from a guide. The classic v2rayN 6.x Windows interface commonly uses SOCKS port 10808 and HTTP port 10809. Some newer versions or core configurations use a mixed listener that accepts both HTTP and SOCKS traffic on one port. Upgrades and migrated settings may also retain older ports, so treat these numbers as examples to investigate—not universal defaults.

Turning off “Allow connections from the LAN” doesn’t free the port; it mainly changes which addresses the listener accepts. For local use, prefer a loopback address. Don’t switch to all interfaces to work around a conflict, or enable extra LAN listeners just to experiment.

Windows: Find the PID and executable path by port

Run the following commands in PowerShell. They only read listener information and do not stop any processes. No results may mean the port isn’t listening, or the core exited after startup failed. If access is denied, try again in an administrator terminal; permission to run a query is separate from whether the core itself should run elevated.

# List TCP listeners with their addresses, ports, and process IDs
Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue |
  Where-Object { $_.LocalPort -in 10808,10809 } |
  Select-Object LocalAddress,LocalPort,OwningProcess

# Get the names, executable paths, and command lines of these listeners
$ownerIds = @(Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue |
  Where-Object { $_.LocalPort -in 10808,10809 } |
  Select-Object -ExpandProperty OwningProcess -Unique)

Get-CimInstance Win32_Process |
  Where-Object { $_.ProcessId -in $ownerIds } |
  Select-Object ProcessId,Name,ExecutablePath,CommandLine

You can also use the built-in netstat command in Command Prompt. The expression below matches local ports so you don’t mistake a connection to remote port 10808 for a local listener. Check the state column too: only LISTENING indicates a TCP listener.

netstat -ano -p tcp | findstr /R /C:":10808 " /C:":10809 "

• Note the PID: The last output column is the process ID. Find it by PID under “Details” in Task Manager; don’t identify the process by name alone.
• Check the path: A core with the same name may have been launched from a different v2rayN folder. Check the executable path and command line to identify which client installation it belongs to.
• Distinguish connection states: TIME_WAIT is not a listening process serving as a proxy endpoint. It does not prove that an app is occupying the port.
• Check the protocol: TCP and UDP use separate port spaces. Use Get-NetUDPEndpoint to check the port only if the log specifically reports a UDP bind failure.

Free the port or change it in settings

Running two copies of v2rayN, leaving one in the system tray after closing its window, or leaving an old core running after the main app exits can all look like a port conflict on startup. Save your current settings first, then choose one fix. Don’t change node addresses, DNS, routing, and listening ports all at once, or you won’t know which change worked.

1. Close duplicate instances

   Check the system tray and choose “Exit” on any v2rayN instance you don’t need. Closing the main window may only minimize it to the tray. Check the port again afterward to confirm the listener is gone.

2. Check for leftover processes

   If the main app has exited but the port is still in use, verify the PID, executable path, and command line under “Details” in Task Manager. Use “End task” only for a leftover core you’ve confirmed is no longer needed. Don’t stop system processes or unfamiliar services.

3. Open the settings

   In versions of v2rayN with the classic menu, go to “Settings” → “Parameter settings” and find the local listener options. In the classic 6.x interface, check “Local listening port” on the “Core: Basic settings” page. In other interfaces, use the SOCKS, HTTP, or mixed-listener fields that are actually shown.

4. Choose an unused port

   To check candidates, replace the numbers in the query with 11808,11809. For separate listeners, verify that each enabled endpoint is free. If the HTTP port is generated as the base port plus 1, check the adjacent port too; don’t assume both fields can be edited independently.

5. Save and restart

   Save the settings so the core reloads them. If it doesn’t restart automatically, exit v2rayN normally and reopen it. Check the log and TCP listener list again to confirm the core in the expected folder now owns the new port.

No process found, but the bind still fails?

Check the address and port in the log, then run the query again. If the error names a different port, searching only for 10808 or 10809 won’t find it. A query run after the failure may also return nothing if the other process has already exited. Once you’ve confirmed the port number, check Windows excluded port ranges if the error is 10013.

netsh interface ipv4 show excludedportrange protocol=tcp
netsh interface ipv6 show excludedportrange protocol=tcp

The output shows a start port and an end port for each range. A range matters only if it includes the port that failed to bind; a long list doesn’t by itself indicate a system problem. System networking components or virtualization features may reserve these ranges. Deleting ranges or disabling system services can affect other network features, so first try an unused port outside those ranges.

• Check the exact address: A listener on 127.0.0.1:10808 is different from one on [::1]:10808. A wildcard bind may also affect other addresses, so keep the full address column when troubleshooting.
• Check security logs: If the bind still fails on multiple ports confirmed to be free, review system or security software logs for blocked activity. Don’t disable protection outright or add broad inbound allow rules.
• Separate local from remote issues: A firewall blocking a remote connection usually causes a connection failure or timeout. A website not loading alone does not prove that a local port is in conflict.

Equivalent commands for macOS and Linux

When using the v2rayN desktop app, check the ports in your current settings and replace the numbers in the commands below. Use lsof on macOS and ss on Linux. Administrator privileges may be needed to see process paths or details. As on Windows, try closing the app that owns the port normally before stopping its process.

# macOS: Check each example port separately
lsof -nP -iTCP:10808 -sTCP:LISTEN
lsof -nP -iTCP:10809 -sTCP:LISTEN

# Linux: Show listening sockets and processes
sudo ss -ltnp '( sport = :10808 or sport = :10809 )'

Update system proxy and app settings

Changing the port fixes the listener, but apps may still be pointed at the old one. This can make it seem like the core is running while apps still can’t connect. In v2rayN, reapply “System proxy” → “Set system proxy”. If that menu isn’t available in your version, use the equivalent automatic system proxy option and verify the address recorded by the system.

You can test the new TCP endpoint in PowerShell. This example assumes you enabled 11808. TcpTestSucceeded : True only means the TCP connection was established; it doesn’t confirm the listener’s identity, that the proxy protocol works, or that the remote node is reachable. Check the PID and make an actual request as well.

Test-NetConnection -ComputerName 127.0.0.1 -Port 11808

Port-in-use FAQs