However, I’m able to access this route fine via web browsers. So it is working correctly, at least for a web browser. I also have other services running on this host, I am not having issues with my other services connecting to https://$service.<mydomain>.duckdns.org.
On the other hand, I found that this route works (http://homeassistant.<mydomain>.duckdns.org:8123) in the app (and also on browser too)
But this route should not be available as it permits insecure connections, so I also need to fix this. For now at least HA works, but there is definitely something wrong as I can not connect via the android app at the moment
EDIT: Adding a note, I don’t yet have a valid cert for the subdomain homeassistant.<mydomain>.duckdns.org (because duckdns certs does not support this), so I can visit https://homeassistant.<mydomain>.duckdns.org only on browsers such as firefox that allow invalid certs. Is the app set up to reject invalid certs? I am planning to switch to cloudflare but have just not done so yet (it is my next task)
Here are my home assistant confs
http:
use_x_forwarded_for: true
trusted_proxies:
- 192.168.1.16 # Nuc
and nginx conf
listen 443 ssl;
listen [::]:443 ssl;
server_name homeassistant.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app 192.168.1.100;
set $upstream_port 8123;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
location /api {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app 192.168.1.100;
set $upstream_port 8123;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
}