How to Fix ‘Address Already in Use’ (EADDRINUSE) Error in Linux

Starting a web server, development environment, Docker container, or background daemon in Linux only to encounter the error Error: listen EADDRINUSE: address already in use :::8080 or bind: Address already in use brings application deployments to an immediate stop. In POSIX operating systems, network communication relies on IP sockets mapped to specific transport layer port numbers. By default, only a single process can bind to a specific combination of IP address, transport protocol (TCP/UDP), and port number at any given moment. When an existing background service, orphaned zombie process, or lingering socket connection in the TIME_WAIT state holds the binding, subsequent requests to bind that port fail with the EADDRINUSE errno code. This practical guide demonstrates how to identify rogue processes holding open ports and release socket bindings cleanly.

Why Does the EADDRINUSE Error Occur?

Socket binding failures occur when the Linux kernel network stack rejects the bind() system call:

  • Lingering Background or Orphaned Processes: An earlier instance of your application crashed, was detached from your terminal, or was suspended in the background without executing clean socket shutdown routines.
  • Sockets Stuck in TIME_WAIT State: When a TCP connection is closed, the initiating side enters TIME_WAIT for up to 60–120 seconds to catch delayed in-flight packets, preventing immediate socket rebinding unless SO_REUSEADDR is set.
  • Conflicting System Daemons: System-installed web servers (such as Apache, Nginx, or systemd-resolved) already claiming default ports (80, 443, or 53).
  • Docker Container Port Forwarding Collisions: A stopped or running container holding host network interface mappings.

Method 1: Identify the Conflicting Process Using lsof

The lsof (list open files) utility directly inspects active socket handles and displays their owning Process IDs (PIDs).

  1. Open your Linux terminal.
  2. Run the following command, replacing 8080 with your conflicting port number:
    sudo lsof -i :8080
  3. Review the output columns. Locate the COMMAND, PID, and USER:
    COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    node    14820 sam     23u  IPv6 128492      0t0  TCP *:8080 (LISTEN)
  4. Terminate the lingering process cleanly using its PID:
    kill -15 14820
  5. If the process fails to terminate gracefully after a few seconds, force kill it:
    kill -9 14820

Method 2: Find and Release Sockets Using ss and fuser

If lsof is not installed in minimal distributions, use standard Linux socket statistics (ss) and fuser.

  1. Query listening TCP sockets and their owning processes:
    sudo ss -tulpn | grep :8080
  2. The output displays the local address and the associated process name and PID:
    tcp   LISTEN 0 511 *:8080 *:* users:(("python3",pid=18234,fd=4))
  3. Alternatively, use fuser to inspect and terminate the occupying process in a single command:
    # Check who is using the port
    sudo fuser 8080/tcp
    
    # Terminate the process immediately
    sudo fuser -k 8080/tcp

Method 3: Resolve TCP Sockets in TIME_WAIT State

If no active PID is returned by lsof or ss, the TCP socket is likely lingering in the kernel TIME_WAIT state.

  1. Verify if the port is stuck in TIME_WAIT:
    netstat -tan | grep 8080
  2. If the output displays TIME_WAIT, the socket will release automatically once the 60-second kernel timeout expires.
  3. To prevent this in development code (such as Node.js, Python, or Go), ensure the socket options include SO_REUSEADDR before calling bind():
    • In Python: sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
    • In C/C++: setsockopt(sockfd, SOL_SOCKET, SO_REUSEADDR, &opt, sizeof(opt));

Method 4: Check for Docker Container Port Conflicts

Docker background containers frequently retain port mappings even after development sessions end.

  1. List all currently running Docker containers:
    docker ps
  2. Check the PORTS column for bindings matching your target port (e.g., 0.0.0.0:8080->80/tcp).
  3. Stop the conflicting container using its Container ID or name:
    docker stop <container_id>
  4. If necessary, prune unused containers and dangling network bridges:
    docker container prune -f

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.