addons: Unable to use without usr/pwd after upgrading from 6.0.2 to 6.1.1
Describe the issue you are experiencing
I have no usr/pwd config. This is config in plugin:
logins: []
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
active: true
folder: mosquitto
anonymous: true
2 main clients:
- zigbee2mqtt
- HA core
After upgrading communication is broken. Error messages are in addon log - see below.
I think this could be source of problem:
Remove mosquitto-auth-plug and replace with mosquitto-go-auth 1.8.2
But i don’t see any info about breaking changes.
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
Which add-on are you reporting an issue with?
Mosquitto broker
What is the version of the add-on?
6.1.1
Steps to reproduce the issue
- Use “no usr/pwd” (anon) config of plugin
- upgrade to 6.1.1
- errors in log, mqtt communication broken …
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
1651863797: New connection from xx.xx.xx.xx:33658 on port 1883.
error: received null username or password for unpwd check
1651863797: Client <unknown> disconnected, not authorised.
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 28 (4 by maintainers)
@mdegat01 wrote: If you really want to enable them on your instance then you can do so with the customize option.
I think it is not true, because doc has no “anonymous” mode anymore.
And i have to reply to “anon mode is dangerous”. Why? I have router, firewall, and my secure LAN. Why double-secure servers inside LAN? Do you lock rooms inside locked house? NO! Yes it is safer to lock also room in locked house. But who do it? It is nonsense.
So let users to decide and bring anon mode back please.
@damclarkd I had just recently worked on a debug option to make this easier and realized I never merged it 😆
Just put in #2477 which adds a
debugoption. When you turn it on you will see debug level logs from both mosquitto and the mosquitto-go-auth plugin. Hopefully that can help you track down what’s going on.