Node.js v21.1.0
[nodemon] app crashed - waiting for file changes before starting...

Question

I ran npm install and then got an error when I run npm start:
Node.js v21.1.0
[nodemon] app crashed - waiting for file changes before starting...
I tried restarting the nodemon server and killing all node processes but I still get the error. I'm a beginner here and I don't know how to continue?
Error: listen EADDRINUSE: address already in use :::5000
    at Server.setupListenHandle as _listen2 (node:net:1872:16)
    at listenInCluster (node:net:1920:12)
    at Server.listen (node:net:2008:7)
    at Function.listen (/Users/charlie/Documents/Web Dev/Team Treehouse/Sequelize Model Validation/sequelize-model-validation/6 - Password Confirmation and Hashing/rest-api/nodemodules/express/lib/application.js:635:24)
    at /Users/charlie/Documents/Web Dev/Team Treehouse/Sequelize Model Validation/sequelize-model-validation/6 - Password Confirmation and Hashing/rest-api/app.js:60:24
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1899:8)
    at process.processTicksAndRejections (node:internal/process/taskqueues:82:21) {
  code: 'EADDRINUSE',
  errno: -48,
  syscall: 'listen',
  address: '::',
  port: 5000
}
Node.js v21.1.0
[nodemon] app crashed - waiting for file changes before starting...

Simon Coates · Answer

If you google that error, that message ("Error: listen EADDRINUSE: address already in use") seems to typically be when you already have something listening on that port. If you have a terminal already running, control-c might kill the process. Otherwise you might need to manually kill the process (which might vary depending on OS), use a different port (if that's something you have control over) or reset your local machine.

Welcome to the Treehouse Community

Looking to learn something new?

Charlie Roberts

Charlie Roberts

Node.js v21.1.0 [nodemon] app crashed - waiting for file changes before starting...

1 Answer

Simon Coates

Simon Coates