Hey team,
I’m trying to configure Duck DNS. I have the add-on installed, configured and running, and I’m attempting to add the advised configuration to configuration.yaml
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
However, when I restart Home Assistant it fails to start until I remove his config. I feel like I’m missing something obvious, but I’m somewhat confused by the documentation.
Does the file exist in the ssl folder?
What is the error you are getting when you run the Configuration validation?
Hi @duceduc
Thanks for the reply. Does the /ssl directory exist by default or do I need to create this. Would this typically be in the /config directory? I was under the impression (probably wrongly) that the DuckDNS addon handled the Let’s Encrypt side of things, but do I need to generate some keys and place them in the /ssl directory? I couldn’t find any documentation that walked through this part
It exist. It is not with config folder but one level below it. You will need samba or ssh & web Terminal add-on to access it.
from samba addon:
Ok thanks,
the files exist
bash-5.0# pwd
/ssl
bash-5.0# ls -ltr
total 12
-rw------- 1 root root 3243 Jun 19 22:41 privkey.pem
-rw------- 1 root root 5963 Jun 19 22:41 fullchain.pem
bash-5.0#
How do you know it has failed to start?
How are you attempting to access home Assistant?
On your local network:
https://<ip_address>:8123 and you need to add a security certificate exception in your web browser.
On a remote network or on your local network with a router that supports hairpinning:
https://your_domain.duckdns.org:<forwarded_port>
Note: https not http in both cases and you can omit :<forwarded_port> if you forwarded to port 433.
@tom_l thanks for your reply
Looks like I was getting confused due to an earlier configuation.yaml error, and that I was then unable to run the Web UI. I checked the logs and Home Assistant has started no issues
I had added an exception to my browser but I was foolishly attempting to access the UI from a bookmark configured to use http, instead of https,
so http://<ip_address>:8123 instead of https://<ip_address>:8123
and I was attempting to access externally without specifying the port
so https://your_domain.duckdns.org instead of https://your_domain.duckdns.org:<forwarded_port>
Now I’ve corrected both those issues, it’s working as expected.
Thanks to @duceduc and yourself for pointing me in the right direction 