Error: listen EADDRINUSE : instance not killed with gulp, but after refresh website
See original GitHub issueby using different versions, e.g. 2.9.1 and windows or linux
I run within gulp with the following two properties
browserSync.init(filesToWatch, {
server: {
baseDir: "*"
},
startPath: "localhost"
});
If I close the gulp process in console and run again the webserver than I get Error: listen EADDRINUSE. If website is refreshed, the process is released and webserver can be started again.
- detection of new port and running instance seems to be broken
- process is not released
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to fix Error: listen EADDRINUSE while using NodeJS?
Save this answer. Show activity on this post. You should try killing the process that is listening on port 80. Killall will kill...
Read more >[Solved]-Node.js - Auto Refresh In Dev-node.js
The EADDRINUSE error is normally due to a connection already open on the specified port. This is probably due to a previous instance...
Read more >throw er / unhandled 'error' event - You.com | The Search ...
Error: listen EADDRINUSE means that the port you're trying to run on is already being used. Try changing to it to use another...
Read more >Let It Crash: Best Practices for Handling Node.js Errors on ...
Let's say we have a server running. It's receiving requests and establishing connections with clients. But what happens if the process crashes?
Read more >Node.js Notes for Professionals
not a liated with o cial Node.js group(s) or company(s). ... 300+ pages ... The following example uses Express to create...
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
I can’t Ctrl-C to exit my dev task. Seems BrowserSync is hanging. I have to close the console and go to taskman and kill the node process.
I’m still having the same problem as @raDiesle on Windows and OSX.
Version 2.9.1 works just fine, but al higher versions (including the mentioned 2.9.3) have the following problems: