How to fix Error listen EADDRINUSE while using nodejs

Question

If I run a server with the port 80  and I try to use xmlHTTPrequest i get this error  Error  listen EADDRINUSE  Why is it problem for nodejs  if I want to do a request  while I run a server on the port 80  For the webbrowsers it is not a problem  I can surf on the internet  while the server is running   The server is     net createServer function  socket        socket name   socket remoteAddress         socket remotePort      console log  connection request from      socket remoteAddress       socket destroy         listen options port     And the request   var xhr   new XMLHttpRequest     xhr onreadystatechange   function         sys puts  State      this readyState        if  this readyState    4            sys puts  Complete  nBody length      this responseText length           sys puts  Body  n    this responseText             xhr open  GET    http   mywebsite com    xhr send

User · Answer

if you want to solve this       node server events js 141         throw er     Unhandled  error  event                Error  listen EADDRINUSE    3000       at Object exports  errnoException  util js 907 11        at exports  exceptionWithHostPort  util js 930 20        at Server  listen2  net js 1250 14        at listen  net js 1286 10        at Server listen  net js 1382 5        at EventEmitter listen  C  sendbox mean node modules express lib application  js 617 24        at Object   C  sendbox mean server js 28 5        at Module  compile  module js 409 26        at Object Module  extensions  js  module js 416 10        at Module load  module js 343 32    change your port number to 8000

User · Answer

Another thing that can give this error  is two HTTP servers in the same node code  I was updating some Express 2 to Express 3 code  and had this     http createServer app  listen app get  port    function                  console log  Express server listening on port     app get  port                      tons of shit   http createServer app  listen app get  port    function                  console log  Express server listening on port     app get  port                                                                               And  it triggered this error

User · Answer

EADDRINUSE means that the port number which listen   tries to bind the server to is already in use   So  in your case  there must be running a server on port 80 already   If you have another webserver running on this port you have to put node js behind that server and proxy it through it   You should check for the listening event like this  to see if the server is really listening   var http require  http     var server http createServer function req res       res end  test         server on  listening  function        console log  ok  server is running         server listen 80

User · Answer

lsof -i 3000  kill -9   lsof -t -i 3000      3000 is a your port    This  lsof -i 3000   command will show PID  kill PID  ex  kill 129393

User · Answer

What really helped for me was   killall -9 node   But this will kill a system process   With   ps ax   you can check if it worked

User · Answer

Got this error when we accidentally had two local Express environments in the same instance pointing to the same port   If you got this far down this list of answers  I hope this will be helpful and solve your problem

User · Answer

Error reason  You are trying to use the busy port number   Two possible solutions for Windows Mac   Free currently used port number Select another port number for your current program     1  Free Port Number  Windows  1  netstat -ano   findstr  4200 2  taskkill  PID 5824  F     Mac  You can try netstat  netstat -vanp tcp   grep 3000   For OSX El Capitan and newer  or if your netstat doesn t support -p   use lsof  sudo lsof -i tcp 3000   if this does not resolve your problem  Mac users can refer to complete discussion about this issue Find  and kill  process locking port 3000 on Mac    2  Change Port Number   Windows  set PORT 5000   Mac  export PORT 5000

User · Answer

EADDRINUSE translates to  The port you are trying to issue app listen   on is being used by other programs   You can use a script like this to check if your port is in use and then change the port in your app listen     var net   require  net    var errors     EADDRINUSE        var isUsed   function port        var tester   net createServer            once  error   function  err              if   errors includes err code                console log  Port is in use  change the port                                     once  listening   function                 tester once  close   function                      console log  You are good to go                                  close                       listen port       You can add other errors in the errors array to check for all sorts of error types as well

User · Answer

There is a way to terminate the process using Task Manager      Note that this solution is for Windows only    Go to the Task Manager  or using the shortcut Ctrl   Shift   Esc  On  Background Processes   find  Node js  processes and terminate them  Right-click them and choose  End Task        Now you should be able to start again

User · Answer

While killing the NODE PORT  it might kill your chrome process or anything that is listening to the same port  and that s annoying    This shell script may be helpful - in my case the port is 1337 but you can change it anytime    LOGIC  CHROME PIDS  pidof chrome  PORT PIDS  lsof -t -i tcp 1337   for pid in  PORT PIDS do  if      CHROME PIDS       pid     then        NOT FOUND IN CHROME PIDS      echo  Killing  pid         ps -p   pid       kill -kill   pid      fi  done  sails lift   OR  node app  OR whatever that starts your node  exit

User · Answer

Seems there is another Node ng serve process running  Check it by typing this in your console  Linux Mac    ps aux grep node   and quit it with   kill -9  lt NodeProcessId gt    OR alternativley use   ng serve --port  lt AnotherFreePortNumber gt    to serve your project on a free port of you choice

User · Answer

The option which is working for me    Run   ps -ax   grep node   You ll get something like    8078 pts 7    Tl     0 01 node server js  8489 pts 10   S      0 00 grep --color auto node      kill -9 8078

User · Answer

The error EADDRINUSE  Address already in use  reports that there is already another process on the local system occupying that address   port   There is a npm package called find-process which helps finding  and closing  the occupying process   Here is a little demo code   const find   require  find-process    const PORT   80  find  port   PORT   then  list    gt      console log  Port    PORT   is blocked  Killing blocking applications        const processIds   list map  item    gt  item pid    processIds forEach  pid    gt  process kill pid  10        I prepared a small sample which can reproduce the EADDRINUSE error  If you launch the following program in two separate terminals  you will see that the first terminal will start a server  on port  3000   and the second terminal will close the already running server  because it blocks the execution of the second terminal  EADDRINUSE    Minimal Working Example   const find   require  find-process   const http   require  http    const PORT   3000     Handling exceptions process on  uncaughtException    error    gt      if  error code      EADDRINUSE         find  port   PORT         then  list    gt            const blockingApplication   list 0          if  blockingApplication              console log  Port    PORT   is blocked by    blockingApplication name                console log  Shutting down blocking application                process kill blockingApplication pid               TODO  Restart server                               Starting server const server   http createServer  request  response    gt      response writeHead 200    Content-Type    text plain      response write  Hello World      response end       server listen PORT       gt  console log  Server running on port    PORT

User · Answer

EADDRINUSE means port of your nodejs app is already in use    Now you have kill the process app running on that port  Find the process id of app by        lsof -i tcp 3000    Now u will get process id from this  Run this       kill -9 processId

User · Answer

Under a controller env  you could use   pkill node before running your script should do the job   Bear in mind this command will kill all the node processes  which might be right if you have i e a container running only one instance  our you have such env where you can guarantee that   In any other scenario  I recommend using a command to kill a certain process id or name you found by looking for it programmatically  like if your process is called  node-server-1 you could do pkill node-server-1   This resource might be useful to understand  https   www thegeekstuff com 2009 12 4-ways-to-kill-a-process-kill-killall-pkill-xkill

User · Answer

I got   Error  listen EADDRINUSE  address already in use    8000   I was trying to look for the process listening to port 8000 and had no luck - there were none  sudo netstat -nlp   grep 8000     It turned out I had app listen 8000  written twice in my script    My assumption is that the interference was happening only in a short time when trying to run the script  so looking for processes listening to the port before and after error didn t show any

User · Answer

The aforementioned killall -9 node  suggested by Patrick works as expected and solves the problem but you may want to read the edit part of this very answer about why kill -9 may not be the best way to do it    On top of that you might want to target a single process rather than blindly killing all active processes   In that case  first get the process ID  PID  of the process running on that port  say 8888    lsof -i tcp 8888   This will return something like   COMMAND   PID    USER   FD   TYPE             DEVICE SIZE OFF NODE NAME node     57385   You   11u  IPv6 0xac745b2749fd2be3      0t0  TCP   ddi-tcp-1  LISTEN    Then just do  ps - actually do not  Please keep reading below    kill -9 57385  You can read a bit more about this here   EDIT  I was reading on a fairly related topic today and stumbled upon this interesting thread on why should i not kill -9 a process       Generally  you should use kill -15 before kill -9 to give the target process a chance to clean up after itself   Processes can t catch or ignore SIGKILL  but they can and often do catch SIGTERM   If you don t give the process a chance to finish what it s doing and clean up  it may leave corrupted files  or other state  around that it won t be able to understand once restarted    So  as stated you should better kill the above process with   kill -15 57385  EDIT 2  As noted in a comment around here many times this error is a consequence of not exiting a process gracefully  That means  a lot of people exit a node command  or any other  using CTRL Z  The correct way of stopping a running process is issuing the CTRL C command which performs a clean exit   Exiting a process the right way will free up that port while shutting down  This will allow you to restart the process without going through the trouble of killing it yourself before being able to re-run it again

User · Answer

In my case I use a web hosting but it  s the same in local host  I used    ps -aef   grep  node     for watch the node process then  the console shows the process with PID  for kill the process you have to use this command   kill -9 PID   where PID is the process id from the command above

User · Answer

Error  listen EADDRINUSE means the port which you want to assign bind to your application server is already in use  You can either assign another port to your application   Or if you want to assign the same port to the app  Then kill the application that is running at your desired port   For a node application what you can try is  find the process id for the node app by    ps -aux   grep node   After getting the process id  do  kill process id

User · Answer

I would prefer doing   killall -15 node   because  kill -15 gives process a chance to cleanup itself  Now  you can verify by  ps aux   grep node  Note  If you don t give process a chance to finish what it is currently doing and clean up  it may lead to corrupted files

User · Answer

Your application is already running on that port 8080   Use this code to kill the port and run your code again  sudo lsof -t -i tcp 8080   xargs kill -9

User · Answer

For other people on windows 10 with node as localhost and running on a port like 3500   not 80      What does not work   killall       command not found ps -aux   grep  node            ps   user x unknown    What shows information but still not does work    ps -aef   grep  node   ps ax  kill -9 61864   What does work    Git Bash or Powershell on Windows     net -a -o   grep 3500    whatever port you are looking for     Notice the PID    far right   I could not get killall to work    so    Open your task manager On processes tab   right click on Name or any column and select to include PID Sort by PID  then right click on right PID and click end task    Now after that not so fun exercise on windows  I realized I can use task manager and find the Node engine and just end it   FYI   I was using Visual Studio Code to run Node on port 3500  and I use Git Bash shell inside VS code   I had exited gracefully with Ctrl   C    but sometimes this does not kill it    I don t want to change my port or reboot so this worked   Hopefully it helps others   Otherwise it is documentation for myself

User · Answer

Windows is always tricky with open source    change the port simply it works  node-inspector --web-port 8099

User · Answer

This error comes when you have any process running on a port on which you want to run your application   how to get which process running on that port   command   sudo netstat -ap   grep  3000      output   you will get the process information which is using that port  tcp        0      0 IPaddress 3000                            LISTEN      26869 node   Now you can kill that process  sudo kill -9 26869

User · Answer

In below command replace your portNumber  sudo lsof -t -i tcp portNumber   xargs kill -9

User · Answer

I have seen this error before  in node  with http client  and as I recall  the problem had to do with not initializing the httpClient or setting bad options in the httpClient creation and or in the url request

User · Answer

I have the same problem too and I simply close the terminal and open a new terminal and run   node server js   again  that works for me  some time just need to wait for a few second till it work again   But this works only on a developer machine instead of a server console

User · Answer

This happened to me because I had my server running in another Terminal window  Closing the connection solved the problem

User · Answer

EADDRINUSE means that the port which we try to listen in node application  is already being used  In order to overcome  we need to identify which process is running with that port    For example if we are trying to listen our node application in 3000 port  We need to check whether that port is already is being used by any other process   step1    sudo netstat -plunt  grep  3000   That the above command gives below result   tcp6       0      0    3000                                         LISTEN      25315 node   step2   Now you got process ID 25315   Kill that process    kill -9 25315   step3   npm run start   Note  This solution for linux users

User · Answer

I had the same issue recently   It means that the port is already being used by another application  express or other software   In my case  I had accidentally run express on 2 terminals  so exiting the terminal using  Ctrl   C  fixed things for me   Run server from only one terminal   Hope it helps others

User · Answer

On Debian i found out to run on port 80 you need to issue the command as root i e   sudo node app js   I hope it helps

User · Answer

For windows users execute the following command in PowerShell window to kill all the node processes   Stop-Process -processname node

User · Answer

This works for me  I m using mac   Run this command  lsof -PiTCP -sTCP LISTEN  This s going to display a list of ports that your syetem is using  Find the PID that your node is running  COMMAND     PID          USER   FD   TYPE             DEVICE SIZE OFF NODE NAME node      17269 hientrq   16u  IPv6 0xc42959c6fa30c3b9      0t0  TCP   51524  LISTEN  node      17269 hientrq   19u  IPv4 0xc42959c71ae86fc1      0t0  TCP localhost 1337  LISTEN    and run kill -9  YOUR PID

User · Answer

Two servers can not listen on same port  so check out if other server listening on same port  also check out for browser sync if its running on same port

User · Answer

Try both commands and it will stop all node process   killall 9 node pkill node npm start

User · Answer

NOOB ERROR FIX  I m new to Node js and setup a webserver listening to port 8080  I ran into the EADDRINUSE error  I tried all the various  kill -9 node  iterations and kept getting   node  no process found  The problem was  I was calling http listen 8080   TWICE in the same blob of code   So the first time it was actually working fine  and the second time it threw an error  If you re getting a  no process found  response when trying to kill the port  try checking to make sure you re only opening the port once

User · Answer

Just a head s up  Skype will sometimes listen on port 80 and therefore cause this error if you try to listen on port 80 from Node js or any other app   You can turn off that behaviour in Skype by accessing the options and clicking Advanced -  Connection -  Use port 80  Untick this        P S  After making that change  don t forget to restart Skype

User · Answer

You should try killing the process that is listening on port 80   Killall will kill all the node apps running  You might not want to do that  With this command you can kill only the one app that is listening on a known port   If using unix try this command    sudo fuser -k 80 tcp

User · Answer

In my case Apache HTTP Server was run on port 80 I solved it by issue the command as root  sudo killall httpd  Update   If Jenkin is installed and running on your Mac    You can check it with sudo lsof -i tcp 8080 If Yes  and You want to stop Jenkins only once  run  sudo launchctl unload  Library LaunchDaemons org jenkins-ci plist

User · Answer

sudo kill   sudo lsof -t -i 80    for force kill      sudo kill -9   sudo lsof -t -i 80    use above cmd to kill particular port and then run your server

[javascript] How to fix Error: listen EADDRINUSE while using nodejs?

Examples related to javascript

Examples related to node.js