-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT failed to connect: Connection refused: Not authorized #13001
Comments
Can you confirm the correct config is in the HA addon MQTT section? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I got the same error after upgrading from 1.26.0-1 to 1.27.0-1. After a complete host reboot, the connection works for some hours. I use an secret on both addons: core-mosquitto and hassio-zigbee2mqtt @Koenkk Should I create a new issue ? |
here some logs: HomeAssitant Addon Log[16:16:47] INFO: Handing over control to Zigbee2MQTT Core ...
|
I try to add the port. But this also does not solve the problem:
|
Can you provide the debug log until it starts failing? |
I had this problem today after restarting my host. Then I stoped Z2M service and Mosquitto broker. Started Mosquitto broker and after a minute Z2M and then it was ok. This is the first time that this happened in 2 years. |
I can confirm @dankocrnkovic. I had to restart my host system, and I got a "502: bad gateway" in the web portal error message along with the "MQTT failed to connect: Connection refused: Not authorized" in the log for zigbee2mqtt. Following his procedure seemed to fix it for me. For reference, I am running Zigbee2mqtt: 1.27.0-1 and Mosquitto broker: 6.1.2 |
How can I extract the debug log ? |
This didn't work for me. I used same credentials on 2 clients, 2 different pc's and everything works fine. It looks like the plugin is broken. thanks |
I have the same problem with both version old (I think 1.22) and 1.27. |
I have to execute the same workaround with every restart |
For the HA addon it is in the |
Are you certain that mosquito is starting up properly after HA is restarted? There's an issue in home-assistant/addons#2618 (comment) alluding to a startup issue if you have mosquito set to Start on boot. |
Thanks. That seemed to be the problem. I disabled Start on boot and left Watchdog enabled and the problem did not occur again |
Confirmed - this just happened to me as well after a restart because of a Zigbee dongle firmware update. |
If you leave the watchdog on and turn off the start on boot you'll be fine and it won't require intervention. Quite counter-intuitive but it works. Mosquito will start up. |
I can confirm the same issue occurred yesterday. Nothing else but restarting the Mosquitto broker add-on and then starting Z2M solved the issue. Before it worked fine from the beginning. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened?
After updating from 1.24.0-1 to 1.25.2-1
it wont start up.
Logs says
I havnt changed any password etc, what can i do to fix this?
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.25.2-1
Adapter firmware version
cantlogintofrontend
Adapter
deconz
Debug log
No response
The text was updated successfully, but these errors were encountered: