Fatal error: Port 8080 is already in use by another process.

[kurtinlane]

Several team members (myself included) ran into this error when running grunt. We got around it by adding 'foundPort = 8080' to node_modules/grunt-contrib-connect/tasksconnect.js on line 153

This is a gross dirty hack to get it to work, but wanted to let you guys know about the issue we found.

Thanks

[donaldpipowitch]

I can confirm this error, but it seems to happen only for our windows users. It seems to only occur for 0.0.0.0, but not localhost. (We used 0.7.1 before, which runs well.)

[vladikoff]

@donaldpipowitch Thanks for checking! We shall investigate 🔍

[donaldpipowitch]

One of our engineers found the culprit.

The "error" was probably introduced by this commit in portscanner: baalexander/node-portscanner@a854ec6
It now correctly destroys a socket instead of ending it. What happens now for us is that 8080 collides with "avast! Web Shield".

[donaldpipowitch]

Any update on this?

[jeanbza]

If avast! is using :8080, what can be done? Shouldn't you just close avast, or switch to a different port?

[donaldpipowitch]

Well, I'm not really a "port" export. You could proablby close avast, but it worked before, so my first question would be: is this a bug now as it doesn't work anymore or was it a bug before as it worked?

[MerlinMason]

Just discovered the same issue now... Seems to occur when starting a server, stopping it and then starting again. Can fix it by killing the Node process's on the port.

$ lsof -i tcp:8080 | grep node | awk '{print $2}'
> PID

$ kill -9 PID

[mayank-gangwal]

I found the same problem in Mac's Terminal. Occurs to me when starting a server, stopping it and then starting again. Restarting terminal window solved the problem.

[erredeco]

for me the error happens no matter what port I specify (Using Windows 10 and "localhost" as host)

[erredeco]

I get the same error on MAC; downgrading to grunt-contrib-connect 1.0.2 solved my problem

[narisunike]

Restart GitHub CodeSpace