Mosquito broker 6.1.2 - All Clients <unknown> disconnected, not authorised

Configuration
,
1

hello,
I really need to solve the following problem.

After update to mosquito 6.1.2 my devices can’t connect to mosquito broker even though all of them are using username and passwords.

1657097927: New connection from 192.168.2.126:60777 on port 1883.
1657097927: Client <unknown> disconnected, not authorised.
1657097927: New connection from 192.168.2.117:50412 on port 1883.
1657097927: Client <unknown> disconnected, not authorised.
1657097928: New connection from 192.168.2.124:59338 on port 1883.
1657097928: Client <unknown> disconnected, not authorised.
1657097930: New connection from 192.168.2.120:61126 on port 1883.
1657097930: Client <unknown> disconnected, not authorised.
1657097930: New connection from 192.168.2.125:63379 on port 1883.
1657097930: Client <unknown> disconnected, not authorised.
1657097930: New connection from 192.168.2.135:60409 on port 1883.
1657097930: Client <unknown> disconnected, not authorised.
1657097930: New connection from 192.168.2.136:53164 on port 1883.
1657097930: Client <unknown> disconnected, not authorised.
1657097931: New connection from 192.168.2.134:56948 on port 1883.
1657097931: Client <unknown> disconnected, not authorised.
1657097933: New connection from 192.168.2.122:56108 on port 1883.
1657097933: Client <unknown> disconnected, not authorised.
1657097935: New connection from 192.168.2.140:60759 on port 1883.
1657097935: Client <unknown> disconnected, not authorised.
1657097938: New connection from 192.168.2.126:55644 on port 1883.
1657097938: Client <unknown> disconnected, not authorised.
1657097938: New connection from 192.168.2.117:56073 on port 1883.
1657097938: Client <unknown> disconnected, not authorised.
1657097939: New connection from 192.168.2.124:63858 on port 1883.
1657097939: Client <unknown> disconnected, not authorised.
1657097941: New connection from 192.168.2.120:64125 on port 1883.
1657097941: Client <unknown> disconnected, not authorised.
1657097941: New connection from 192.168.2.125:53609 on port 1883.
1657097941: Client <unknown> disconnected, not authorised.
1657097941: New connection from 192.168.2.135:62090 on port 1883.
1657097941: Client <unknown> disconnected, not authorised.
1657097941: New connection from 192.168.2.136:49629 on port 1883.
1657097941: Client <unknown> disconnected, not authorised.
1657097942: New connection from 192.168.2.134:54424 on port 1883.
1657097942: Client <unknown> disconnected, not authorised.
1657097944: New connection from 192.168.2.122:50877 on port 1883.
1657097944: Client <unknown> disconnected, not authorised.
1657097946: New connection from 192.168.2.140:53397 on port 1883.
1657097946: Client <unknown> disconnected, not authorised.
1657097949: New connection from 192.168.2.126:61250 on port 1883.
1657097949: Client <unknown> disconnected, not authorised.
1657097949: New connection from 192.168.2.117:56640 on port 1883.
1657097949: Client <unknown> disconnected, not authorised.
1657097950: New connection from 192.168.2.124:62615 on port 1883.
1657097950: Client <unknown> disconnected, not authorised.
1657097952: New connection from 192.168.2.120:54959 on port 1883.
1657097952: Client <unknown> disconnected, not authorised.
1657097952: New connection from 192.168.2.125:58130 on port 1883.
1657097952: Client <unknown> disconnected, not authorised.
1657097952: New connection from 192.168.2.135:61508 on port 1883.
1657097952: Client <unknown> disconnected, not authorised.
1657097952: New connection from 192.168.2.136:52601 on port 1883.
1657097952: Client <unknown> disconnected, not authorised.
1657097953: New connection from 192.168.2.134:62570 on port 1883.
1657097953: Client <unknown> disconnected, not authorised.
1657097955: New connection from 192.168.2.122:58937 on port 1883.
1657097955: Client <unknown> disconnected, not authorised.
1657097957: New connection from 192.168.2.140:49427 on port 1883.
1657097957: Client <unknown> disconnected, not authorised.
1657097960: New connection from 192.168.2.126:53279 on port 1883.
1657097960: Client <unknown> disconnected, not authorised.
1657097960: New connection from 192.168.2.117:57507 on port 1883.
1657097960: Client <unknown> disconnected, not authorised.
1657097961: New connection from 192.168.2.124:51802 on port 1883.
1657097961: Client <unknown> disconnected, not authorised.
1657097963: New connection from 192.168.2.120:64468 on port 1883.
1657097963: Client <unknown> disconnected, not authorised.
1657097963: New connection from 192.168.2.125:59139 on port 1883.
1657097963: Client <unknown> disconnected, not authorised.
1657097963: New connection from 192.168.2.135:57487 on port 1883.
1657097963: Client <unknown> disconnected, not authorised.

I really need to downgrade to 6.0.1 as soon as possible, because I have many many automations that have stopped working. Unfortunately my backup (30 days) don’t have this version and I don’t know how to downgrade the add on manually (I don’t even know if is possible)

Can anyone please upload version 6.0.1 as a backup so I can just restore this version ???

Awaiting the pleasure of your reply

1 Like
2

Is it just me who has this problem ??? Nobody else?

3 Likes
3

I’m seeing this problem now, trying to find a solution

2 Likes
4

I had the same problem. I have reinstalled the add-on. After that it worked again.

1 Like
5

In my case the Zigbee2Mqtt addon caused those problems.

I had to configure the server, user and password in the Zigbeet2Mqtt addon configuration. Somehow it doesn’t work without it anymore.

server: mqtt://core-mosquitto:1883
user: my_user
password: my_password

Please see MQTT | Zigbee2MQTT

1 Like
6

This is expected as the latest release of mosquitto does not allow anonymous logins, so if you’ve previously configured the mqtt integration without a login, you’ll need to set up an mqtt user and reconfigure the integration with this user info.

But this issue is different. The Mosquitto Server stops connections even though all of them are using username and passwords.

Restarting the server fixes the issues for me, but it does reappear after updating HASS.

7

I had the same problem, editing the Mosquitto broker config in HA and saving fix it for me (config seems to have been corrupted)

6 Likes
8

I will name my first born after you, this saved me! Thanks a million

1 Like
9

This one did the trick for me as well! Simply edited the file in the Mosquitto Configuration page, using the 3 dots at the top and choosing edit in yaml. The file looked in a good shape but somehow it still was corrupted. I just added a line and removed it again to activate the save button. After the save, mosquitto automatically restarts and all worked perfectly again!

Thanks a million!

Michel

7 Likes
10

Yes! Spent several hours trying to resolve this problem, and your advice was gold! Thank you!

11

Yeah, just need to restart addon or simply re-edit config.

1 Like
12

thanks a lot. spent about good 3 days finding s solution without checking the forum.
changing anonymous :true from false would be any issue?

image

13

I’m in love with you.
Wasted 2 hours of my life trying to fix Zigbee2mqtt
Not only was the problem in Mosquitto, but also with such a simple solution.

1 Like
14

image
image1246×326 17.5 KB

if you are wondering how to set anonymous to false

in my case it did not help

15

this also did not help me,
as far as i know i have nothing using MQTT right now (removed the two addon’s that did) and i still get unauthorized error logged every 2 mins or so

16

This was by far the simplest solution and worked 100%! Thanks.

17

So this is weird…
I updated the config file restart the addon and it seemed to fix the issue.
However, every time I shut down HA, All devices are gone and I get unauthorized access in the log.
Stopping both addons and restarting them fixes the issue. Not really sure what to do… :frowning:

3 Likes
18

I’ve had the same issue since updating. I’ve worked around it by setting the username/password in the Mosquito configuration file - this seems to survive reboots.

This implies to me that the connection from this add-on to access home assistant users is broken on startup - so the addon starts without access or without users (but works once it’s fully up and running).

19

Same errors here.

The thing is, everything is working for a couple of days, and suddently ALL clients are unable to connect anymore with the error above using username and password.

Restarting Mosquitto broker add-on works, but the issue will inevitably occur again.

20

I suddenly got the same error, no update to mqtt or HA recently, still stuck on an old version, if I restart HA or mqtt they all work, but 5-6 hours later they stop working, I tried now to edit the file as described above, hope it does not repeat but I doubt it.