So I have been running Home Assistant for a while now and everything is great…except…I am almost crying out of despair trying to get encryption to work. I tried about 1 million times, new install etc… Here is what I have done now:
- Install new HASS (using virtual machine, tried all the same things on the Raspberry though)
- Login and create one user
- Install the DuckDNS addon, following configuration
lets_encrypt:
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: xxxxx
domains:
- xxx.duckdns.org
aliases: []
seconds: 300
- Installed Samba addon so I can modify the config when it doesn’t boot to the UI
- Set up port forwarding (I tried all combinations of 443 and 8123, currently have 443 to 443 as this is what most guides explain. This has no effect at all on the below mentioned problem)
- Started the DuckDNS addon and got the certificate files under /ssl
- Then here is where it goes wrong and I cannot figure it out. According to all guides I went through, the next step is to add the “http” section to the configuration.yaml. So this now looks like this:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Nothing else is in the config besides the default (remember, completely new and clean install)
Now if I add one or both of the lines to the config, HASS doesn’t allow me to use the Webinterface anymore. I can still access with Samba, but I cannot open the UI. Removing the lines from the config let’s it boot normally again, but well…encryption does not work.
I am now officially lost…tried everything and as stated a couple of times, started with a complete new and clean installation, added nothing besides what I described above…
Is there anything I am missing, or does anyone have a clue why it doesn’t start when I add the http lines?