v2rayN Port in Use: Fix a 10808 Conflict on Windows

Find the process using the port, change v2rayN’s local listening port, then update your browser and terminal proxy settings.

At a glance

This guide is for Windows users who see a 10808 bind error when starting v2rayN. Check the startup log for the port, then use PowerShell to identify the listening process. If it’s a duplicate instance, exit it normally. If the other service needs to keep running, change v2rayN’s local port instead. Finally, verify the local listener, browser proxy, and terminal proxy separately so a stale address isn’t mistaken for a node issue.

Check the startup log for a bind error

Start with the latest v2rayN startup log. Note the address, port, and exact error message. If it says listen tcp 127.0.0.1:10808, the issue is with a local TCP listening port. This is not a remote port in your subscription or a server port in the node editor.

Error: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Cause: Windows rejected a duplicate bind to that address and port. Fix: Find the process listening on the port shown in the log, then decide whether to exit the duplicate instance or move v2rayN to another port.

Error: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

Cause: Windows rejected the socket bind. One possible reason is that the port is in a system-excluded range. Fix: If no listening process is found, check the TCP excluded port ranges and try a port outside them.

The local proxy port connects the app to the core. A browser sends requests to the local listener first; the core then selects an outbound connection according to its routing rules. Changing nodes won’t fix a local bind conflict if the listener never starts.

App requestLocal listenerCore inboundRoutingOutbound connection

Find the process using a port on Windows

After the error appears, leave other apps open. In PowerShell, check TCP listeners on 10808 and match each process ID to its process name. If the log shows a different port, replace 10808 in the command with that port.

$listeners = Get-NetTCPConnection -LocalPort 10808 -State Listen -ErrorAction SilentlyContinue
$listeners | Select-Object LocalAddress, LocalPort, OwningProcess
$listeners | Select-Object -ExpandProperty OwningProcess -Unique |
  ForEach-Object { Get-Process -Id $_ | Select-Object Id, ProcessName, Path }
  • Check 127.0.0.1:10808 and 0.0.0.0:10808 first. The latter listens on all IPv4 addresses, including the loopback address. If the only result is ::, note it; whether it also occupies the IPv4 port depends on the socket configuration.
  • If the result points to a core launched by another v2rayN instance, check the process path and running instances. Exit the extra instance from its tray menu, then run the query again. Closing the main window may leave the tray process running.
  • If the process belongs to an app that needs to keep running, leave it alone and choose a new port for v2rayN. If you can’t identify it by its path, check the PID in Task Manager’s Details tab. Don’t end a process based on its name alone.

No results only means no matching listener was found at the time of the query. If the error disappears quickly, run the query again while reproducing it. If the log keeps reporting an access-permission error, run the following command in Windows Terminal to see whether 10808 falls within an excluded range. If it does, change the port rather than removing a system reservation.

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

Change v2rayN’s port: move off 10808

The steps below use 18080 as an example. It’s only a candidate; availability depends on your PC. In v2rayN 7.x, the mixed port can serve as a single local endpoint for both HTTP and SOCKS. If your version shows separate HTTP and SOCKS ports, update each field and note which protocol uses each port.

  1. Check the candidate port

    Change the port in your PowerShell query to 18080. Make sure there’s no existing TCP listener and check that it’s outside the excluded ranges. If the settings show related ports, check each one too.

  2. Open the inbound settings

    In the v2rayN main window, open Settings → Parameter Settings and find the local listening port under Core Basic Settings. If your version has a Mixed Port field or separate HTTP and SOCKS ports, use the fields shown in your version.

  3. Save and reload

    Replace the conflicting local port with your candidate and save. If the log doesn’t show the core restarting, exit v2rayN from the system tray and reopen it. Don’t change the remote port for a node in the server list.

  4. Verify the new listener

    Check the log for bind errors on the new port, then find the process listening on 18080. Make sure it’s the core launched by the current v2rayN instance. If you only use the proxy on this PC, keep it bound to loopback; enabling LAN access won’t resolve a port conflict.

Update the proxy address in browsers and terminals

Even after the local listener is back, some apps may still use the old address. Update one setting and test it before moving on to the next. The table assumes the mixed port is now 18080; if HTTP and SOCKS use separate listeners, enter the port for the relevant protocol instead.

Configuration sourceWhere to update itExample
Windows system proxyIf v2rayN manages the system proxy, select “Set system proxy” from its tray menu again. Then check the actual address in Windows Settings → Network & Internet → Proxy.127.0.0.1:18080
Browser-specific proxyCheck the browser’s own proxy settings or any active proxy extension. Keep the protocol you were using and update only the host and port. If you use the system proxy, make sure the browser is set to follow it.SOCKS5 127.0.0.1:18080
Terminal proxyCheck command-line options, environment variables in the current session, and the tool’s own settings. If the old value is in a terminal startup script, edit it and open a new terminal to verify the change.HTTPS_PROXY=http://127.0.0.1:18080

Test an explicit proxy first so you can tell whether the proxy works without relying on environment variables. Run these two commands in Windows Command Prompt. The first tests an HTTP proxy; the second tests SOCKS5 and resolves the destination hostname through the proxy. A mixed endpoint can be tested with either protocol. For separate endpoints, use the port assigned to each one.

curl.exe --noproxy "" --proxy http://127.0.0.1:18080 --max-time 15 -I https://example.com
curl.exe --noproxy "" --proxy socks5h://127.0.0.1:18080 --max-time 15 -I https://example.com

In the HTTP proxy test, 200 Connection established means the CONNECT tunnel was created; check the following response headers to confirm the destination replied. If the connection to 127.0.0.1:18080 fails, check the local listening address and port first. If the local endpoint accepts the connection but the destination times out, use core logs from the same time to investigate routing and outbound connectivity.

Port conflict FAQs

The process using the port is also a core. Can I just close it?

Check the process path and start time first. If it’s a core launched by another v2rayN instance, exit that instance from its tray menu, then check the port again. If you can’t tell which instance owns it, change the port for the current instance instead.

Why does the log show 10809 after I changed 10808?

Use the latest log and check which process is listening on 10809. Then check the separate HTTP port in the settings, other local inbounds, and any custom configuration to find which endpoint is actually trying to bind. Don’t change a port that’s already working.

Why does the terminal still use the old port when the browser works?

In PowerShell, run Get-ChildItem Env:*PROXY* to view proxy variables in the current session. If you still see 10808, update the variable used by your tool and check persistent settings or startup scripts. If the variable is already correct, check whether a command-line option is overriding it.

The error stopped after restarting. Do I still need to change the port?

First, make sure the listener on 10808 belongs to the core launched by the current v2rayN instance. Then test the browser and terminal separately. If both work, keep the existing port. If the conflict only returns after sign-in, check whether two instances start with Windows.

Download v2rayN