No errors or warnings in either the HASS or Caddy 2 logs. Ping my_subdomain.duckdns.org works.
Partial restore only Caddy 2 1.0.4 and all works again.
No errors or warnings in either the HASS or Caddy 2 logs. Ping my_subdomain.duckdns.org works.
Partial restore only Caddy 2 1.0.4 and all works again.
There are at least two repositories for a Cady 2 addon that I can find. Which one are you using?
Did you check the breaking changes before updating?
I’m running einschmidt/addon-caddy-2
I don’t see any breaking changes regarding Caddy 2 or proxies. Neither Read Me nor Changelog for new version gives no hint of issues. I did look at them before update.
Based on your question should we rethink automatic updates for add-ons? Auto Update was not on in this case.
Yeah automatic updates are a bad idea. I always turn them off so I can read the changes before updating.
I suggest you open an issue with the maintainer of the addon:
It’s working perfectly on 2 domains here. What exactly is your issue?
Have opened issue.
With 1.0.4 I can open HA with url https://hass.mysubdomain.duckdns.org. With 1.0.5 and no other changes that url gives “Unable to connect to Home Assistant”. Have cleared cache, tried other browsers. I suspect this is related to my Caddyfile and/or local DNS making the new version unhappy.
Also might relate to unsupported status. With 2021.9.0 I will again become supported and will then retry Caddy 2 1.0.5