HTTPS inside LAN | New Version of HA iOS App

Installation
21

On your lan’s dns make your external domain name (eg example.duckdns.com) point to the internal ip address of your HA server, (eg 192.168.1.200).

22

Hi, my ISP’s router does not have that option. So will need to go either with a separate dns (pihole) or a separate router.

23

Use another DNS server…you can use HA’s addon…:thinking:

24

Hi,
2 steps forward, 1 step back.
This works when I set this DNS on a PC
Then I get
dnsmasq[208]: query[A] myxxxxx.duckdns.org from 192.168.1.22
dnsmasq[208]: config myxxxxx.duckdns.org is 192.168.1.97
dnsmasq[208]: query[A] wpad.localdomain from 192.168.1.22

However, when setting this on a Iphone,Ipad it with IOS 14 it doesnt. Looks like its triggering DNS over HTTPS.
When I put the same URL that works from a PC in my Iphone I get entries in dnsmasq pointing to
]: cached 27.courier-push-apple.com.akadns.net is
…
So no local DNS call is performed…
Back to square I again.

25

Hi everyone,
there is a solution for the problem I described in my first post.

The solution is to use the NGINX Home Assistant SSL proxy plugin.

My HTTP configuration is the following.

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.0.0/16
  ip_ban_enabled: true
  login_attempts_threshold: 5

While my plugin’s configuration is:

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

In this way, home assistant is listening HTTP port 8123 and HTTPS port 443 tanks to the plugin, so I use internal and external URLs. Of course, fullchain.pem and privkey.pem correspond to Let’s Encrypt’s certificates.

1 Like
26

Hi,
using the combination of duckdns & nginx worked perfectly for me!

1 Like