Mosquito broker not working

Ive been having problems with zigbee devices ever since the new update to zigbee2mqtt.
The logs for that look okay. But logs for mosquito are as follows. Can you help as to whats going on? I deleted mosquito and started again and yet the problems persist

Thanks

Mosquitto broker
2025-05-27 14:25:03: Client mqttjs_af9c00b6 disconnected, not authorised.
2025-05-27 14:25:16: New connection from 172.30.33.6:41730 on port 1883.
2025-05-27 14:25:16: Client mqttjs_7cf71542 disconnected, not authorised.
2025-05-27 14:25:30: New connection from 172.30.33.6:51578 on port 1883.
2025-05-27 14:25:30: Client mqttjs_edff248b disconnected, not authorised.
2025-05-27 14:26:12: New connection from 172.30.32.2:39102 on port 1883.
2025-05-27 14:26:12: Client closed its connection.
2025-05-27 14:26:16: New connection from 172.30.32.1:46073 on port 1883.
2025-05-27 14:26:16: Client 64sYhimUsv4cpuJ3NMvZIT disconnected, not authorised.
2025-05-27 14:27:02: Client 2XQHQOotZI7maHvjHaKxa2 disconnected.
s6-rc: info: service legacy-services: stopping
[13:27:10] INFO: Service restart after closing
2025-05-27 14:27:10: mosquitto version 2.0.21 terminating
2025-05-27 14:27:10: Saving in-memory database to /data//mosquitto.db.
[13:27:10] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[14:32:25] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[14:32:26] INFO: Starting NGINX for authentication handling…
s6-rc: info: service legacy-services successfully started
[14:32:26] INFO: Starting mosquitto MQTT broker…
2025-05-27 14:32:26: Warning: Mosquitto should not be run as root/administrator.
2025-05-27 14:32:26: mosquitto version 2.0.21 starting
2025-05-27 14:32:26: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-05-27 14:32:26: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-05-27 14:32:26: ├── Username/password checking enabled.
2025-05-27 14:32:26: ├── TLS-PSK checking enabled.
2025-05-27 14:32:26: └── Extended authentication not enabled.
2025-05-27 14:32:26: Opening ipv4 listen socket on port 1883.
2025-05-27 14:32:26: Opening ipv6 listen socket on port 1883.
2025-05-27 14:32:26: Opening websockets listen socket on port 1884.
2025-05-27 14:32:26: mosquitto version 2.0.21 running
2025-05-27 14:32:26: New connection from ::1:60888 on port 1883.
2025-05-27 14:32:26: Client disconnected due to protocol error.
[14:32:27] INFO: Successfully send discovery information to Home Assistant.
[14:32:27] INFO: Successfully send service information to the Supervisor.
2025-05-27 14:32:46: New connection from 172.30.32.1:42681 on port 1883.
2025-05-27 14:32:46: New client connected from 172.30.32.1:42681 as 3m1jqGzqXsIKB0h1mPYwvq (p2, c1, k60, u’homeassistant’).
2025-05-27 14:32:46: Client 3m1jqGzqXsIKB0h1mPYwvq disconnected.
2025-05-27 14:32:46: New connection from 172.30.32.1:45757 on port 1883.
2025-05-27 14:32:46: New client connected from 172.30.32.1:45757 as 72eZFK1MdKYevy6fDnBCRk (p2, c1, k60, u’homeassistant’).
2025-05-27 14:33:27: New connection from 172.30.32.1:57575 on port 1883.
2025-05-27 14:33:27: New client connected from 172.30.32.1:57575 as 2tH2lQgbaJj20U25SYhAoE (p2, c1, k60, u’mqtt-user’).
2025-05-27 14:33:27: Client 2tH2lQgbaJj20U25SYhAoE disconnected.
2025-05-27 14:33:27: Client 72eZFK1MdKYevy6fDnBCRk disconnected.
2025-05-27 14:33:27: New connection from 172.30.32.1:60999 on port 1883.
2025-05-27 14:33:27: New client connected from 172.30.32.1:60999 as 3Eih04wG4DSdLAAUZ7SZol (p2, c1, k60, u’mqtt-user’).
2025-05-27 14:33:27: Client 3Eih04wG4DSdLAAUZ7SZol disconnected.
2025-05-27 14:33:27: New connection from 172.30.32.1:46645 on port 1883.
2025-05-27 14:33:27: New client connected from 172.30.32.1:46645 as 2WJwn2AbKFtISvkhIAZI79 (p2, c1, k60, u’mqtt-user’).
2025-05-27 14:34:12: New connection from 172.30.32.2:34494 on port 1883.
2025-05-27 14:34:12: Client closed its connection.
2025-05-27 14:34:43: New connection from 172.30.33.6:35936 on port 1883.
2025-05-27 14:34:43: New client connected from 172.30.33.6:35936 as mqttjs_c4c9a997 (p2, c1, k60, u’mqtt-user’).
2025-05-27 14:36:12: New connection from 172.30.32.2:34270 on port 1883.
2025-05-27 14:36:12: Client closed its connection.
2025-05-27 14:36:28: Client 2WJwn2AbKFtISvkhIAZI79 closed its connection.
2025-05-27 14:36:51: New connection from 172.30.32.1:50593 on port 1883.
2025-05-27 14:36:51: New client connected from 172.30.32.1:50593 as 5GvPzbYlALj57fTPqS0Oef (p2, c1, k60, u’mqtt-user’).
2025-05-27 14:38:12: New connection from 172.30.32.2:54860 on port 1883.
2025-05-27 14:38:12: Client closed its connection.
2025-05-27 14:40:12: New connection from 172.30.32.2:59126 on port 1883.
2025-05-27 14:40:12: Client closed its connection.
2025-05-27 14:42:12: New connection from 172.30.32.2:42414 on port 1883.
2025-05-27 14:42:12: Client closed its connection.
2025-05-27 14:44:12: New connection from 172.30.32.2:50206 on port 1883.
2025-05-27 14:44:12: Client closed its connection.
2025-05-27 14:46:12: New connection from 172.30.32.2:40578 on port 1883.
2025-05-27 14:46:12: Client closed its connection.
2025-05-27 14:48:12: New connection from 172.30.32.2:33426 on port 1883.
2025-05-27 14:48:12: Client closed its connection.
2025-05-27 14:48:27: Client mqttjs_c4c9a997 disconnected.
2025-05-27 14:48:41: New connection from 172.30.33.6:52142 on port 1883.
2025-05-27 14:48:41: New client connected from 172.30.33.6:52142 as mqttjs_0b2a8c4e (p2, c1, k60, u’addons’).
2025-05-27 14:49:09: Client mqttjs_0b2a8c4e closed its connection.
2025-05-27 14:49:14: New connection from 172.30.33.6:39582 on port 1883.
2025-05-27 14:49:14: New client connected from 172.30.33.6:39582 as mqttjs_9e631a73 (p2, c1, k60, u’addons’).
2025-05-27 14:49:19: Client mqttjs_9e631a73 disconnected.
2025-05-27 14:49:33: New connection from 172.30.33.6:51290 on port 1883.
2025-05-27 14:49:33: New client connected from 172.30.33.6:51290 as mqttjs_4b023dea (p2, c1, k60, u’addons’).
2025-05-27 14:50:12: New connection from 172.30.32.2:51510 on port 1883.
2025-05-27 14:50:12: Client closed its

Hi,

What kind of problems?
The MQTT Broker logs are looking oké I think

These are normal:

2025-05-27 14:46:12: New connection from 172.30.32.2:40578 on port 1883.
2025-05-27 14:46:12: Client closed its connection.

It is the supervisor watchdog checking that the broker is running. There’s a switch on the Mosquitto add-on page labelled “Watchdog”. If you turn this off the messages should stop. Though after this test I would recommend turning it back on so the supervisor can restart the broker if it stops for some reason.

These are the only abnormal logs I spotted:

2025-05-27 14:26:16: Client 64sYhimUsv4cpuJ3NMvZIT disconnected, not authorised.
2025-05-27 14:32:26: New connection from ::1:60888 on port 1883.
2025-05-27 14:32:26: Client disconnected due to protocol error.