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

9001 port is used on windows 10 #1580

Closed
pherbel opened this issue Jan 30, 2020 · 15 comments
Closed

9001 port is used on windows 10 #1580

pherbel opened this issue Jan 30, 2020 · 15 comments

Comments

@pherbel
Copy link

pherbel commented Jan 30, 2020

After I restarted my windows 10, I can't start my MQTT docker image. Previously it has worked.
I'm getting this error:

ERROR: for mqtt Cannot start service mqtt: Ports are not available: listen tcp 0.0.0.0:9001: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

After I checked the port usage, it seems system service (PID 4) uses the 9001 port. It is very interesting.

Does anybody have the same issue?

@ralight
Copy link
Contributor

ralight commented Feb 4, 2020

You could try removing -p 9001:9001 from your docker command. If you haven't configured that port for use in your mosquitto config, then that part isn't doing anything anyway.

@pherbel
Copy link
Author

pherbel commented Feb 5, 2020

Yeah I removed and the image starts, but I'm getting errors

Client disconnected due to protocol error.

@ralight
Copy link
Contributor

ralight commented Feb 6, 2020

Ok, my guess would be that you are getting a mismatch between your listener and client in terms of being configured for unencrypted MQTT/encrypted MQTT/MQTT over unencrypted websockets/MQTT over encrypted websockets. Can you check what your broker configuration is, and whether the client matches what you would expect?

This shows the config options you might have:

# Plain MQTT
listener 1883

# Encrypted MQTT
listener 8883
cafile <path>
certfile <path>
keyfile <path>

# Plain WebSockets
listener 8000
protocol websockets

# Encrypted WebSockets
listener 8001
protocol websockets
cafile <path>
certfile <path>
keyfile <path>

You could also try using a different client to connect and see if that has the same problem.

@sfitts
Copy link

sfitts commented Apr 22, 2020

I've started seeing the same thing -- though it is obviously not an MQTT issue. Suddenly port 9001 was already in use by "System" and so my Mosquitto container wouldn't start.

Based on this issue -- cretueusebiu/valet-windows#131 it appears that Intel started using this port for some of their drivers. Bad Intel.

There does not appear to be a way to configure that, so it is time to move MQTT to a different port.

ralight added a commit that referenced this issue Apr 23, 2020
Port 9001 is used by Intel drivers on Windows, so some users are
suddenly seeing a problem.

Issue #1580.
@ralight
Copy link
Contributor

ralight commented Apr 23, 2020

@sfitts Thanks for the tip on Intel, it's good to know the cause. I've push a change to the examples in the readme to use port 8080 instead.

@ralight
Copy link
Contributor

ralight commented Apr 30, 2020

I think this can be closed now.

@ralight ralight closed this as completed Apr 30, 2020
sidhant007 pushed a commit to sidhant007/mosquitto that referenced this issue May 15, 2020
Port 9001 is used by Intel drivers on Windows, so some users are
suddenly seeing a problem.

Issue eclipse#1580.
@martinandersen3d
Copy link

martinandersen3d commented May 23, 2020

SOLVED :: SOLUTION:

This is a intel graphics card software related issue on windows 10.

How to fix:

In windows, go to:

  • Star menu
  • Type: Services
  • Find the service called: Intel(R) Graphics Command Center Service
  • Rightclick > Properties > Startup type = Disabled

This fixed the problem for me.. :-)

ralight added a commit that referenced this issue Jun 17, 2020
Port 9001 is used by Intel drivers on Windows, so some users are
suddenly seeing a problem.

Issue #1580.
@shaolonger
Copy link

Intel(R) Graphics Command Center Service

That works for me, thx very much!

@jinweijie
Copy link

Solved.

This is a intel graphics card software related issue on windows 10.

How to fix:

In windows, go to:

Star menu
Type: Services:
Find the service called: "Intel(R) Graphics Command Center Service"
Rightclick > Properties > Startup type = Disabled

This fixed the problem for me.. :-)

Thanks! Also works for me! Hey Intel, what are you doing?

@self-debug
Copy link

Solved.
This is a intel graphics card software related issue on windows 10.
How to fix:
In windows, go to:
Star menu
Type: Services:
Find the service called: "Intel(R) Graphics Command Center Service"
Rightclick > Properties > Startup type = Disabled
This fixed the problem for me.. :-)

Thanks! Also works for me! Hey Intel, what are you doing?

Works for me too! Thanks a lot!

@RajahArumugam
Copy link

Worked for me Thanks

@barnesk9
Copy link

OMG!!! After 3 months of trying to resolve this issue this worked THANK YOU SO MUCH!!!!!!!!!!!!!

@hasanbasri1993
Copy link

Solved.

This is a intel graphics card software related issue on windows 10.

How to fix:

In windows, go to:

Star menu
Type: Services:
Find the service called: "Intel(R) Graphics Command Center Service"
Rightclick > Properties > Startup type = Disabled

This fixed the problem for me.. :-)

solved
thanks you

@klassisch
Copy link

disabling Intel(R) Graphics Command Center Service worked for me as well. Win10 Pro stock without Docker, VM etc. Thanks a lot for sharing this fix!

@wll1234
Copy link

wll1234 commented May 20, 2021

SOLVED :: SOLUTION:

This is a intel graphics card software related issue on windows 10.

How to fix:

In windows, go to:

  • Star menu
  • Type: Services
  • Find the service called: Intel(R) Graphics Command Center Service
  • Rightclick > Properties > Startup type = Disabled

This fixed the problem for me.. :-)

It works! thanks.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests