Discussion
Question for the #homeAssistant fedifolk:
I'm running #HAOS as a VM on proxmox, and have it configured to automatically renew a #letsEncrypt certificate using DNS01 validation and Mythic Beasts.
The cert has expired and hasn't renewed. The web UI just says "Unable to connect to Home Assistant" (see attached) image. I've tried rebooting the VM in the hope that the certificate renewal process would restart, but that didn't work.
How do I fix this with no UI access?
Full marks to @barnett for replying with a solution quickly: open the page in a private browser window, accept the expired cert, and you get the web UI 👌
So, looking in the logs for the LetsEncrypt app on HAOS, it was loading at boot time, but failing to connect to the #mythicBeasts API endpoint (see attached image).
What's interesting is the timestamps on the log entries. I absolutely was not trying to do this at 05:00 (although the date is correct).
But when I then ran the renew manually (by starting the Let's Encrypt app from the HA web UI), it worked, with the correct timestamps! I've got my web UI back, and a valid certificate.
I'd guess the failure was connected to the bad time values (SSL handshakes with the MythicBeasts API endpoints failing), but the homeassistant graphs are full of correctly timed data, and so are all the event logs. It doesn't look like it was the system time that was wrong, in other words 🤔
I am confused!
So, it would appear that when you runs "apps" in HA OS, they are in fact docker containers. It looks like the Let's Encrypt app on my system failed to sync it's time correctly when it started automatically, cascading to the SSL handshake for the DNS updates failing, and the cert renewal not happening.
Why did it work when I subsequently ran it manually? Who knows...
@WiteWulf I had the same issue recently. I had assumed that I messed something up in the set up.
Install bonfire.cafe
Get the full app experience
