question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: listen EADDRINUSE : instance not killed with gulp, but after refresh website

See original GitHub issue

by 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.

  1. detection of new port and running instance seems to be broken
  2. process is not released

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
ghostcommented, Sep 8, 2015

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.

0reactions
W0lfw00dcommented, Oct 21, 2015

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:

  1. Detection of new port and running instance seems to be broken
  2. The process is not released
Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found