This one just seems totally stale and it’s a really crippling issue.
Sorry - just don’t know who/where else to turn to!
Have you tried setting up a reverse proxy, that handles the SSL?
Setting up Nginx Proxy Manager add-on is just a few clicks.
1 Like
I’ll give that a go. I guess it’s worth a try. Any idea how I come OFF the DuckDNS Let’s Encrypt method and go onto Nginx? Setting it up it looks like I’d simply ADD the Nginx add-on and leave everything else as is which doesn’t seem like it can be right? Surely there would be a conflict? How do I tell DuckDNS/Let’s Encrypt that Nginx is playing too now? Thanks!
From my understanding you shouldn’t have to do anything with DuckDNS. You install the addon, forward ports 80 & 443 to NGINX, delete port forwarding for 8123, setup the proxy for your DuckDNS domain and create a new certificate in the process. Then you change your HA http config from SSL to proxy and that should be it.
I have my own domain with a wildcard SSL certificate, but basically that should work the same.
ah, for benefit of any future readers, looks like I need to take (or at least comment) out the bits in my configuration.yaml under http
Edit: also removing the S from internal_url: https: making it internal_url: http: