I’ve installed HAOS on to a NUC PC. I’m struggling to enable remote access using Duckdns.
My problem is that HA wont start if I add the ssl_certificate line to configure.yaml (the ssl_key is fine).
configuration.yaml:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
My Duckdns Add-on configuration is:
aliases: []
domains:
- ***.duckdns.org
lets_encrypt:
accept_terms: true
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem
seconds: 300
token: ----
I have noticed that if I delete the pem files from the ssl directory and restart the add-on the pem files are recreated but still will not load.
Any ideas?
The Netherlands, 28-08-2022
Hi all,
I have the same issue with the .pem files. The files are created with the DuckDNS addon. I’m sure they are in the ssl directory because I can see them in the Windows file explorer witch I can use because of installing Samba share in HA.
When I add the http: section in de configuration.yaml:
http:
ssl_certificate: ‘/ssl/fullchain.pem’
ssl_key: ‘/ssl/privkey.pem’
I validate the yaml and it seams OK. Then I do a HA restart but HA will not start again.
Fortunately from Windows I can edit the HA configuration.yaml and so I can delete the http: section in the yaml file and then after a restart of my raspberry pi HA starts again.
Btw I can reach my HA over the internet (http) so DuckDNS works but its not over a secure line (https).
So HELP, what could be wrong?
Kind regards from the Netherlands
Arie-Jan