Mosquitto: 9001 port is used on windows 10

[pherbel]

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]

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]

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

Client disconnected due to protocol error.

[ralight]

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]

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 -- https://github.com/cretueusebiu/valet-windows/issues/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]

@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]

I think this can be closed now.

[martinandersen3d]

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.. :-)

[shaolonger]

Intel(R) Graphics Command Center Service

That works for me, thx very much!

[jinweijie]

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]

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]

Worked for me Thanks

[barnesk9]

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

[hasanbasri1993]

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]

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!