Hi all, I am trying to access remotely using duckdns but if I put the following in configuration.yaml HA cannot start:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
`
Is this maybe outdated ?
P.s. Supervised install
Hi all, I am trying to access remotely using duckdns but if I put the following in configuration.yaml HA cannot start:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
`
Is this maybe outdated ?
P.s. Supervised install
Are you sure HA is not starting, or did you forget that http://homeassistant.local won’t work any more because now you need to use https://… ?
Yes, it seems to get stuck, no response, “lost connection…” and I have to edit the yaml file via ssh to remove the offending lines. Then it starts as normal.
My searches lead me to think it’s a problem of ssl certificates. The path /ssl/fullchain.pem doesn’t lead to the certs or something like that. However if I search in Samba I can find the files in /ssl.
A quick update in case it might help anyone. I have put my previous NUC back as the HA server and the “offending” lines in the configuration.yaml file don’t cause any start-up issues. Not saying there aren’t issues, the logs show plenty, but it starts up fine.
I wish I knew why.