I am having the same issue. Anyone??
I first tried using my existing domain name and getting my key from the Let’sEncrypt Add-on at the Hassio store.
When that failed to work, I preceeded to try the DuckDNS method since there seems like a lot more documentation on this process.
Both methods I get a positive confirmation that everything was successful and I get the certificate and key created in the Hassio directory: root/ssl/
I have tried these version of port-forwarding
8123 --> 8123 --> 192.168.1.205
443 --> 8123 --> 192.168.1.205
80 --> 8123 --> 192.168.1.205
I have the following lines in the configuration.yaml file
--http:
----base_url: mysite.duckdns.org:8123
----ssl_certificate: /ssl/fullchain.pem
----ssl_key: /ssl/privkey.pem
when I try to access Hassio via: https://mysite.duckdns.org I get “This site can’t provide a secure connection”
I have no issues accessing the site through http://mysite.duckdns.org
What am I doing wrong? Is there another step I am missing? I have tried all of these steps on a brand new setup of Hassio as well as my existing setup.
I have an indenting question for the http: section. When I look at everyone’s configuration.yaml file online, there is NO indent for the ‘http:’ and a 2 space indent for everything under it. If I use this indentation method, my frontend will fail to load once I add the ssl_certificate and ssl_key sections. If I indent the ‘http:’ 2 spaces and everything else 4 spaces, I have no issue. I have checked spacing and confirmed no tabs more times than I can count. What is the correct way to indent this section and could this be causing me the problem I am having?
Thanks for any help