a few questions, tested to add cert to my home assitant instance (vm) and definitely didnt like what i ended up with since it appears that homeassistant doesnt allow http and https side by side without doing some fancy nginx proxy stuff.
so i decided to revert back to what i had before by simply removing the two pem files and changing back the two lines i had under http: in configuration.yaml
unfortunately even after a reboot most, if not all addons now misbehave.
even “file editor” is broken and shows “401: Unauthorized”
not sure whats going on, all my changes has been reverted to the way it was before.
i even restored to old snapshot of core 2021.6.3 plus config and still no luck.
clearing all site data in browser seems to have fixed it.
but i don’t get why it is needed, i mean if authentication to addons is no longer valid then setup a new one, i did login to homeassistant successfully and can look at everything else.
Thanks for this. I was having the same issue going back from using duckdns as my remote access. Here was my circumstances for the record:
I am trying to downgrade/uninstall from remote access via duckDNS – which has worked very well for over a year.
The process of getting duckDNS access to work involves installing the duckDNS add-on and adding SSL certs to HA to convert HTTP to HTTPS secure browser connections.
I now want to ‘back out’ of this and go back to HTTP for a short time whilst I decide on my next alternative remote access method – Cloudflare, Tailscale etc etc.
After I uninstall the duckDNS add-on I still have access locally but the certificates now do not match my config giving me a security error in my browser (not a big problem) but not allowing the Android HA app to connect complaining of mismatched security certificates.
Attempting to resolve this I ‘#’ out the 3 lines in configuration.yaml:
and with the android app too. However when I try and go into one of the side bar utilities in HA like file editor or terminal or HACS or grafana I get the error 401 Unauthorized error.