Desiring to access HA over https, I used the let’s encrypt add-on to generate the certificates (port challenge) and wrote configuration.yaml this way:
http:
server_port: 8124
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Now I could access my site with https:// but I couldn’t reach it over the LAN and my ecowitt devices became unavailable. When I searched for a solution to that I found a lot of discussions using DuckDNS and the NGINX proxy. But I have a static ip and a registered domain and don’t need or want a dynamic DNS.
So I tried using NGINX without DuckDNS and it hasn’t gone well. I forwarded ports 443 and 80 to ports 443 and 80 on the HA internal ip. I installed the NGINX add-on with this configuration:
domain: ko0y.org
hsts: max-age=31536000; includeSubDomains
certfile: fullchain.pem
keyfile: privkey.pem
cloudflare: false
customize:
active: false
default: nginx_proxy_default*.conf
servers: nginx_proxy/*.conf
and the configuration.yaml set to this:
http:
server_port: 8124
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
With this setup, I can access HA over the LAN and using http://, but not with https://. In other words, it acts as it did before installing the certificates or NGINX. The log says NGINX is running.
Do I have the configuration for NGINX wrong, or can it not be used without DuckDNS? If the latter, is there another way to use my https certificates while still being able to use the ecowitt integration and access HA over the LAN? Thanks for any help.