So…
I was using the DuckDNS add-on to expose HA to the outside world… instead of “doing it right” with a proxy…
(I also pay for Nabu Casa so, having both was kinda dumb, but I did it for… reasons… nevermind… ha.)
Decided to fix the breakage this caused after an ISP change where the new provider has CGNAT anyway, so nothing will be reaching the house ever again other than through reverse VPN tunnels…
So I uninstalled DuckDNS add on, and removed the segment of the config that looked like this completely to kill SSL…
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# # base_url: https://REDACTED.duckdns.org:8123
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
HA is happily non-SSL now, which was the intention, Android mobile app is happy again with the certificates (it couldn’t do a local connect in https ever, iOS would let you accept the risk) but, here’s the weirdo…
I can’t remember what the thing is called that passes add-on web interfaces from their Docker containers under the hood through the HA webserver, and pages… but …
If I go to http://REDACTEDlocalIP/lovelace/main - Add On web interfaces refuse to load now, like removing DuckDNS and that config stanza left something expecting an https connection somewhere. No browser error, acts like HA simply won’t hand out the pages over http.
If I go to my Nabu Casa URL https://REDACTED/ui.nabu.casa/REDACTED/dashboard for any of the add ons, they come up fine.
So maybe two things here…
- DuckDNS modify something and not return it to default on uninstall? Might be a bug report.
- And should the http: stanza in configuration.yaml be completely commented out for a boring old HAOS non-ssl install?
What did I accidentally pooch up here? 
No intention of going back to https/SSL internally… will do my own proxy and VPN junk to get off of my new ISPs little CGNAT world, I’ve got that part no problem, and can hairpin the connection properly on site when I set that up… but I’d like to see the system behaving in non-SSL mode completely first.
I’m missing something that’s breaking the Add On web pages only. Normal Lovelace pages and such work fine. Seems like some under the hood Docker stuff maybe… and I’m an old Unix head so grabbing logs or command line isn’t a problem, I’m just not sure where thre DuckDNS Add On messes with things during install.
Thanks for any thoughts.