Skip to content
Back to the playbook

Freeing a port stuck with EADDRINUSE

Node.jsrevision 1

Diagnostic tree

  1. In progressNode process crashes on startup with EADDRINUSESomething else already has this exact port bound. The fix depends on whether that's a leftover instance of your own app or a different service that legitimately needs the port.
View the whole map (7 more steps)
  • Find out what's already using the port
  • Nothing is bound to that port right now
  • Is the process holding the port an old instance of this same app?
  • Fix: terminate the leftover process
  • Root cause: a different, legitimate service owns that port
  • Confirm the port is free and the app starts
  • Resolved

What to test

Node process crashes on startup with EADDRINUSE

Something else already has this exact port bound. The fix depends on whether that's a leftover instance of your own app or a different service that legitimately needs the port.

What happened?