DuckDNS doesn't start working - error in configuration.yaml?

Configuration
1

I try to get working the duckdns add on.

I try to follow the instruction page at https://www.home-assistant.io/addons/duckdns/

I added these lines to my configuration.yaml file:
http:
base_url: mydomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

When I validate the configuration file I get this error:

Invalid config for [http]: not a file for dictionary value @ data[‘http’][‘ssl_certificate’]. Got ‘/ssl/fullchain.pem’
not a file for dictionary value @ data[‘http’][‘ssl_key’]. Got ‘/ssl/privkey.pem’. (See /config/configuration.yaml, line 26). Please check the docs at https://home-assistant.io/components/http/

This is the configuration of the add-on
{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “My-duckdns-token”,
“domains”: [
“mydomain.duckdns.org:8123”
],
“seconds”: 300
}

This is an excerpt of the add on logfile:
Thu Mar 7 14:55:46 CET 2019: KO
Thu Mar 7 15:00:47 CET 2019: KO
Thu Mar 7 15:05:48 CET 2019: KO
Thu Mar 7 15:10:49 CET 2019: KO
Thu Mar 7 15:15:50 CET 2019: KO
Thu Mar 7 15:20:51 CET 2019: KO
Thu Mar 7 15:25:52 CET 2019: KO
Thu Mar 7 15:30:53 CET 2019: KO
Thu Mar 7 15:35:54 CET 2019: KO
Thu Mar 7 15:40:55 CET 2019: KO
Thu Mar 7 15:45:56 CET 2019: KO

What is going wrong?

2

Did you ever work this out? Sorry to drag up an old post but I’m having the exact same issue and can’t find a solution through my Google and forum searches.

3

Here is my current working DuckDNS/LetsEncrypt add-on config:

accept_terms: true
algo: secp384r1
certfile: certfile.pem
keyfile: privkey.pem
1 Like
4

I worked out the issue. Like the OP I was following the guide but I eventually realised the timing of setting up the Port Forwarding on the router was not clear in the guide - the error described occurs if it hasn’t been set up correctly. All sorted now.