Exactly my sense of humour 
While scanning my Greenbone server running the latest Community Containers I get the above result. I’m using the default configuration/docker-compose file from greenbone.github.io
Is there a way to secure the MQTT access?
Best regards
Christian
I had a laugh as well 
You can safely disable the port directive for the MQTT server if you’re running everything on one host, I guess. At least that is what I did.
Could you explain how to resolve this issue?
I am using GCE docker version.
I came across this issue, too a couple of days ago when testing an all in one docker host deployment which should be placed outside of our corporate firewall.
I’m also very interested how to solve this issue.
Basically just remove the public port in the mqtt broker:
mqtt-broker:
restart: on-failure
image: greenbone/mqtt-broker
ports:
- 1883:1883
networks:
default:
aliases:
- mqtt-broker
- broker
to
mqtt-broker:
restart: on-failure
image: greenbone/mqtt-broker
networks:
default:
aliases:
- mqtt-broker
- broker
Why was the port in the configuration or what is the port needed for in Greenbone?
I’m just guessing, but could be for a distributed cluster setup.
Perhaps someone at Greenbone can help and tell us for what this port is used and if it can safely disabled in an all in one docker environment.
@sven1
Is a distributed cluster setup possible with the community edition?
@bellum
Yes, an explanation is of course good.
A note should be added to the doc for a secure configuration.
Just remove that statement. It’s not necessary. I think it’s just in there by accident.
Hi,
i was receiving MQTT broker does not require authentication, currently i dont have any MQTT service running on my server.
grep 1883 /etc/services
mqtt 1883/tcp # Message Queuing Telemetry
mqtt 1883/udp # Message Queuing Telemetry
sudo netstat -tulpn | grep LISTEN
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 3214312/docker-prox
i can’t find configuration which you added in MQTT without authenticaton Post