Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught Error: listen EACCES 127.0.0.1:50005 #271

Closed
maxocoin opened this issue Jan 18, 2019 · 9 comments
Closed

Uncaught Error: listen EACCES 127.0.0.1:50005 #271

maxocoin opened this issue Jan 18, 2019 · 9 comments

Comments

@maxocoin
Copy link

maxocoin commented Jan 18, 2019

I upgraded to Scatter 10.1.1 and I can't login using Firefox or Chrome.

When I open Scatter's console I see:

Uncaught Error: listen EACCES 127.0.0.1:50005
    at Object._errnoException (util.js:1024:11)
    at _exceptionWithHostPort (util.js:1046:20)
    at Server.setupListenHandle [as _listen2] (net.js:1334:19)
    at listenInCluster (net.js:1392:12)
    at doListen (net.js:1501:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
events.js:183 Uncaught Error: listen EACCES 127.0.0.1:50006
    at Object._errnoException (util.js:1024:11)
    at _exceptionWithHostPort (util.js:1046:20)
    at Server.setupListenHandle [as _listen2] (net.js:1334:19)
    at listenInCluster (net.js:1392:12)
    at doListen (net.js:1501:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

I disabled the firewall just in case but I see the same issue.
Running on Windows 10

@Soleone
Copy link
Contributor

Soleone commented Jan 18, 2019

It sounds like on your machine the port 50005 might already be in use by another program.

Could you try using the Resource Monitor app in Windows 10 to try to figure out if you see something that is using port 50005 next time you see this error? https://stackoverflow.com/a/23718720

@maxocoin
Copy link
Author

maxocoin commented Jan 18, 2019

No,
I already checked that before submitting the ticket (but using netstat, nice trick ;-) )
image

@maxocoin
Copy link
Author

I disabled the antivirus and the firewall, always the same error

@nsjames
Copy link
Contributor

nsjames commented Jan 22, 2019

Are you running docker?

I see you're on windows and for windows the port being used isn't the only thing, it could also be reserved.
Try putting netsh int ipv4 show excludedportrange tcp into cmd/console and seeing if the ports 50005 and 50006 are included in a reserved range there.

@maxocoin
Copy link
Author

maxocoin commented Jan 22, 2019

nsjames, thank you.
I didn't know about that!!!
Yes, they are in the reserved range:
50001 50010
Now what?
Un-reserve those ports? Force the use of those port even when they are reserved?
Or is there a way to change the port that Scatter is listening to (and won't that break the webs finding scatter?
Cheers
JD

I think that this should be detected by scatter and display some work around

@nsjames
Copy link
Contributor

nsjames commented Jan 22, 2019

@maxocoin You can try manually releasing them by altering and using this command:

netsh int ip delete excludedportrange protocol=tcp startport=49998 numberofports=99

Otherwise you'll have to find the application that is using those ports and disable/uninstall it.
Sadly you can't change the ports that are being listened to since the apps define that port inside the scatter-js library. Without a way to have an initial connection then there's also no way to find a way to change ports either since it would effectively make scatter into a port-scanner.

@maxocoin
Copy link
Author

Thank you.
It gives me access denied :-(

C:\WINDOWS\system32>netsh int ipv4 delete excludedportrange protocol=tcp startport=50001 numberofports=10
Acceso denegado.

Any tips for find out the software that reserved the ports?

@maxocoin maxocoin reopened this Jan 22, 2019
@maxocoin
Copy link
Author

maxocoin commented Jan 23, 2019

Duplicate of #245
I disabled hyper-V restarted and Scatter started to work

@4Ykw
Copy link

4Ykw commented Apr 26, 2019

Maybe in the future, we can set this to use local6 instead. There will be extra goodness, protection in that area and it will not be a problem for Windows damn stupid default way of reserving ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants