I’m running Home Assistant in Docker, and I’m a bit confused about the correct way to add iFrames for other containers.
Let me explain. I’m using Docker Compose, and I’ve built a Home Assistant stack that includes several services, including Node-RED. Home Assistant itself is reverse-proxied using Caddy, which I also use for other services like WordPress and some additional servers.
Here’s my issue: I recently bought a Zigbee USB dongle and plan to use it with Zigbee2MQTT. I’ve noticed that on Home Assistant Core, users can add services to the sidebar (such as Zigbee2MQTT or Node-RED), and I’d like to do the same.
However, I’m worried I’ll have to do the same thing I did with Node-RED. For it, I had to reverse-proxy it in order to avoid the Your connection is not private warning caused by the self-signed certificates.
So my question is: is there a way to have Home Assistant available at something like https://home.domain.com and still display an assigned iframe without having to reverse-proxy the iframe service as well?
For example, my iframe config currently looks like this:
type: iframe
url: https://node-red.redacted.gr
This works perfectly fine, but to have it work, I have to reverse proxy Node-Red
The reason I’d like to avoid reverse-proxying yet another service is that it feels like it increases my attack surface.