No experience with cady, but I’ll post my config with NGINX and you can see if there is any similar overlap. I’m using SWAG which runs in Docker and includes NGINX, following the guide here:
I have the letsencrypt cert set for wildcard to allow for subdomains (more explanation in the linked guide). For zigbee2mqtt, it is configured the reverse proxy with requiring http auth (on top of its own auth for 2 layers of login securing) with the config below:
################################################################################
### SUBDOMAIN 5 ZigbeeMQTT########################################################
server {
listen 443 ssl;
root /config/www;
index index.html index.htm index.php;
server_name zigbee2mqtt.yourdomain.duckdns.org;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
auth_basic "Restricted";
auth_basic_user_file /config/nginx/.htpasswd;
include /config/nginx/proxy.conf;
proxy_pass http://192.168.0.101:8086;
}
}
See this article to configure the http auth in nginx
Once the reverse proxy is configured properly, for the iframe config in home assistant:
- title: zigbee2mqtt
type: panel
badges: []
cards:
- type: iframe
url: https://zigbee2mqtt.yourdomain.duckdns.org
aspect_ratio: 100%
This is how it will look - initial login:
Once logged in with http auth and logged into zigbee2mqtt: