Bug: notification images aren't downloaded in case of certificate mismatch

[lab02-research]

Bug: notification images aren't downloaded in case of certificate mismatch

[andystewart999]

Thanks very much!

[andystewart999]

OK, I'll give that a whirl. Thanks for the research and effort :-)

[LAB02-Admin]

Hey @andystewart999, good point - I'll add the option to ignore image certificate errors in the next release, thanks.

[LAB02-Admin]

Hey @andystewart999, I was busy adding the ignore certificate errors for images function in HASS.Agent (actually completed it), but afterwards I found out that's not the issue 😅

It's because when you're using duckdns, you can't access HA locally anymore. I've fixed it by using the NGINX Home Assistant SSL proxy addon.

Configuration steps:

• Install NGINX Home Assistant SSL proxy addon
• Configure as follows:

certfile: fullchain.pem
cloudflare: false
customize:
  active: false
  default: nginx_proxy_default*.conf
  servers: nginx_proxy/*.conf
domain: your_domain.duckdns.org
hsts: max-age=31536000; includeSubDomains
keyfile: privkey.pem

• Start the addon, it'll give errors in the log, don't mind those
• You probably changed the http section of configuration.yaml for the duckdns addon, change it to the following:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

• Reboot Home Assistant
• If you set port forwarding in your router, you need to change the destination port from 8123 to 443
• You can ofc keep the source port the same, as long as it forwards to 443

You should now be able to access your Home Assistant instance both through both the duckdns url and its local IP, and use the local IP to retrieve notification images.

Let me know if you have any issues!