It seems that community loves to feed everything via proxies - ESPHome and some other solutions do not have native admin web page TLS support, and this is on purpose.
Quick note - I run everything on single host Docker containers with macvlan network type.
Quickly did spin up NPMPlus, got Let’s Encrypt wildcard cert to it - everything works fine when I reach from my machine with local DNS zone and https://esphome.mydomain.net . But if I try to create Web page dashboard in HA with the same FQDN I get “…refused to connect.” And it seems HA somehow just resolves hostname directly via Docker instead of FQDN.
But when I connect to HA container itself and run NSLOOKUP esphome.mydomain.net - it correctly resolves to NPMProxy’s IP. ping esphome.mydomain.net does the same.
Of course I just can introduce additional set of DNS records like esphome-proxy.mydomain.net and use them in HA dashboards and everything will work, but I’m curious why HA neglects FQDNs?
1 post - 1 participant