If you've been building and testing a Node.js server, you've probably run into this cryptic wall at least once:

Error: listen EADDRINUSE
  at errnoException (net.js:614:11)
  at Array.0 (net.js:704:26)
  at EventEmitter._tickCallback (node.js:192:40)

Frustrating, right? Your server won't start, nothing seems broken in your code, and a full system reboot feels like overkill. Let's fix this properly.

What Does EADDRINUSE Actually Mean?

EADDRINUSE stands for Error: Address Already In Use. It means the port your Node.js app is trying to listen on — say, port 3000 — is already occupied by another process. This commonly happens when:

• A previous instance of your server didn't shut down cleanly (e.g., you hit Ctrl+C mid-run).

• Another app is already bound to that port.

• A zombie process is still holding onto the port in the background.

The Fix: Kill the Process Occupying the Port

You don't need to reboot. You just need to find and kill the process using that port.

On macOS / Linux

Run this single command (replace 3000 with your port number):

kill -9 $(lsof -t -i:3000)

This uses lsof to look up the process ID (PID) occupying port 3000, then immediately kills it with kill -9.

Source: This solution was originally posted on Stack Overflow by Atta Ur Rahman and later refined by the community. License: CC BY-SA 4.0.

On Windows 11 (PowerShell / CMD)

Since lsof is a Unix tool, Windows users need a slightly different approach.

Step 1: Find the PID using the port:

netstat -ano | findstr :3000

You'll see output like:

TCP    0.0.0.0:3000    0.0.0.0:0    LISTENING    12345

The last number (12345) is the PID.

Step 2: Kill the process by PID:

taskkill /PID 12345 /F

After the Kill

Once the port is freed, restart your Node.js server normally:

node server.js

Or with npm:

npm start

It should come up cleanly without the EADDRINUSE error.

Pro Tip: Prevent This From Happening Again

Add a graceful shutdown handler in your Node.js app so the port is always released when the process exits:

process.on('SIGINT', () => {
  server.close(() => {
    console.log('Server closed. Port released.');
    process.exit(0);
  });
});

This way, even hitting Ctrl+C won't leave a zombie process behind.

Summary

No reboot needed. Just a quick port cleanup and you're back in action.

Found this helpful? The original Stack Overflow answer is here — give it an upvote if it saved you a reboot!

Graphic Summary: