Has anybody else been having CloudMQTT issues today? My OwnTracks device tracker has stopped working and the CloudMQTT is giving a security warning saying their SSL/TLS certificate expired (the expiry date seems to be today).
1 Like
Yea still seeing this. Owntracks works again on my phone but HASS still won’t connect to it. The website is still showing an expired certificate.
1 Like
As a workaround I changed the port in my config file from 2xxxx to 1xxxx (keep the other 4 numbers the same) and got it working again. I think the 1xxxx ports are not using SSL, so its not ideal but should get you running until they get the certificate updated.
I’ve got it working with SSL again. I had restarted HASS several times and it made no difference (even though OpenSSL was saying the certificate was valid), what worked was adding certificate: auto to my mqtt configuration and restarting HASS. The configuration now looks like this:
mqtt:
broker: *.cloudmqtt.com
port: 2****
certificate: auto
username: *****************
password: *****************
Somehow, with the new SSL certificate configuration, this is now needed when it was not needed before. I tried changing the configuration back, in case this was just coincidence and it had been fixed anyway, but it broke again with the same SSL error.
4 Likes
Thanks for the tip! The certificates were apparently fixed in 0.79.2, but I was still seeing SSL cert errors in my cloudmqtt logs. Adding certificate: auto to my mqtt config and restarting home assistant worked for me (running 0.80.3)!
Hi there,
mqqt is still the most troubling integration in Home Assistant for me.
I also had expired certificates in MQTT, while home assistant itself was fine!
Maybe someone can confirm this: Restarting Home Assistant does not restart MQTT. In this case MQTT would stick with the old certificate. Restarting MQTT manually fixed the outdated certificates.
Should it restart on a new certificate automatically? This is what Let’s encrypt needs.
btw: I get my certicates not from the internal LE addon.