As the title says, I can’t access the frontend after upgrade.
I’ve tried to downgrade aswell but same errors occurs.
Can someone help me figure out what’s wrong?
homeassistant.log:
https://hastebin.com/adumotitaq.sql
I’m getting this too as of today on 0.72.1 with a previously valid-for-another-month ssl certificate.
Reverting to 0.72.0 has had no effect.
I think i managed to fix my problem.
Check if you can access the certs using homeassistant user! 
1 Like
Yeah just got a permissions error on cert.pem, thanks!
This is happening to me as well it started last night with 72.0 and continued with upgrade to 72.1. I was able to accesss front end at 5am gmt. Not sure what changed I can’t access on home network or outside.
It seems this is my problem too. How can I give permission to homeassistant user?
I removed the file cert.pem and re-run the process to generate a certificate. I think the issue was that the cert was trying to renew whilst HomeAssistant was still running, but I’m not entirely sure.
Edit:
I was using this guide to set it up, the comments suggest you need to give the homeassistant user rights to stop/start the service to renew the cert.
I tried that using dehydrated and I don’t have permissions to mkdir.i think I might have to run from the beginning.
I’m making a few assumptions about your setup here, but are you running the process as the homeassistant user or another account?
If you’re trying to do this on another account it won’t work.
I am running on the homeassistant user account. After stopping the homeassistant process. I have run it before as that is how I had my original cert.
I used this same guide.
Don’t forget to check that the cron job is running as homeassistant and not another user. This is what I think ultimately caused my issue, my cron was running as “pi” and not “homeassistant”.
Use crontab -u homeassistant -e to check. If there are no entries, it’s not the homeassistant user running the renewal and you’ll get permissions errors.
It seems my crontab was running as homeassistant but using pi as the folder to place the cert files. Restarting hopefully that does it.
I think you’re on the right track, let me know how you get on!
Whelp. I can’t remove the old certs as homeassistant does not have permission.
Yes, that’s expected as that’s how we both got into this mess. Switch back to your other account, sudo rm /path/to/cert.pem (or just purge the entire folder), switch to the homeassistant user and start again.
I ran have removed the certs I ran the dehydrated script it seemed successful then asked for sudo password for homeassistant user.
Yes, you need to edit the visudo things I mentioned previously to allow the script to start/stop homeassistant as required.
Ok I am a little lost on how to do that.
Got it. Thank you for your help!! I did as you said removed the certs changed the permissions checked my crontab. I can now see my front end. Thanks you!