Error: listen EADDRINUSE: address already in use :::5000
See original GitHub issueDescribe the bug After upgrading to version 4.3.2, terminal throws always this error: Error: listen EADDRINUSE: address already in use :::PORT
Socket.IO server version: 4.3.2
Socket.IO client version: 4.3.2
When i changed port it worked again. Platform:
- Device: Apple Macbook Pro
- OS: MacOS Monterey version 12.0.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Node / Express: EADDRINUSE, Address already in use - Kill ...
First, you would want to know which process is using port 3000 sudo lsof -i :3000. this will list all PID listening on...
Read more >How to kill server when seeing “EADDRINUSE: address ...
Nodejs listen EADDRINUSE: address already in use. The Problem. When trying to restart a Node application, the previous one did not shut down ......
Read more >Error: listen EADDRINUSE: address already in use :::5000
Close port before reinitializing server. Actual behaviour. [0] [nodemon] starting `node server.js` [0] events.js:292 [0] throw er; ...
Read more >Node.js Error: listen EADDRINUSE: Address already in use
This quick article shows you how to solve a common error you might confront when working with Node.js. The Problem When developing a...
Read more >How to find and terminate a Windows Processes by Port
[nodemon] starting `node ./app.js` events.js:292 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE: address already in use :::8080 at Server ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
MacOS Monterey has some new features that uses ports 5000 and 7000. I think port 5000 is used by a feature called AirPlay Receiver. If you want to use that port for your own needs then you should disable that from System Preferences. Same can said for port 7000 but i’m not sure what new feature of MacOS uses that for
I’m closing this issue, as I don’t think this is related to Socket.IO. Please reopen if needed.