I updated HA to 2022.7.0 and things went south. The first issue I observed was I could not edit automations. I tried restoring the partial backup the system update made to go back to 2022.6 but that emptied my /config folder! I still had access to the UI so chose a full restore from June 4 @ 3:00 am. That got the system back but now I can only access it via http://homeassistant.local:8123 rather than https://my.domain.ca/my-dashboard as I have been doing for > 6 months. How do I fix this???
Sounds more like an issue with your configuration of the webserver that tells your domain where to point.
How have you configured that to work?
For example I have my domain with cloudflare. I run a nginx webserver seperately to HA and have config files for each subdomain i want to expose. Those configs need to have the correct LAN IP address and port of each app i’m trying to access and on cloudflare it needs to know my public/WAN IP address.
I use cloudflare dns for my public resolution of host.my_domain.com and internal powerdns server with local IP’s for host(s).my_domain.com. The URL correctly resolves locally to 192.168.1.104.
It looks like my Let’s Encrypt certificate expired but I just finished setting that up again and restarted Nginx Proxy but it still won’t let me in…
[7/6/2022] [7:08:34 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-5 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:398:12)
at ChildProcess.emit (node:events:527:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:527:28)
at Pipe.<anonymous> (node:net:709:12)
