Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
0
Members

Can't start server? EADDRINUSE

A topic by CuddleTheif created Apr 14, 2016 Views: 1,589 Replies: 5
Viewing posts 1 to 4

I'm trying to use superpowers for the first time but when I start it the console gives me this error no matter what port I use:

Error: listen EADDRINUSE 127.0.0.1:80
at Object.exports._errnoException (util.js:856:11)
at exports._exceptionWithHostPort (util.js:879:20)
at Server._listen2 (net.js:1234:14)
at listen (net.js:1270:10)
at net.js:1379:9
at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:63:16)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:82:10)

If I had to guess, EADDRINUSE could be "Error, address in use"... It looks like you set the port to 80, which might be taken by another program like Skype. I'd try to change the port to something with 4 digits since some of the lower ones are reserved. I have mine set to 4237, which might be the default value since I don't think I've had to change it.

Another thing to try after changing the ports (if that doesn't work) is the 32-bit version of Superpowers. Last time I used the 64-bit version, I was having random disconnection issues.

I tried using a different port and the 32 bit version but I still get this error

Error: listen EADDRINUSE 127.0.0.1:4237
at Object.exports._errnoException (util.js:856:11)
at exports._exceptionWithHostPort (util.js:879:20)
at Server._listen2 (net.js:1234:14)
at listen (net.js:1270:10)
at net.js:1379:9
at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:63:16)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:82:10)

I wish I knew more about debugging this sort of thing :/

All I can find about "EADDRINUSE" is that the ip:port is being used by another program or service... But it wouldn't make sense that all the ports you've tried so far wouldn't work. Hopefully someone more knowledgeable about this will be able to help you. It might be a good idea to add your OS to your original post since it might be something someone else ran into on a specific system.

(+1)

SOLVED!
For anyone else having this error. Your main and build port numbers, in settings, MUST BE DIFFERENT!

Oh nice! That also explains why it seemed like all the ports were being used by other programs. Glad you found out what was causing the problem! :D