Installing DuckDNS for the first time and getting the exact error when I start the service.
Excactly same problem here. First time install on rPi
Same error here! Recovering from crashes SD. Think error is on their side and not yours or mine.
I’m also getting this error. Brand new Hass.io install, not on CGNAT (was, but got unique IP from ISP), all ports properly forwarded, can access remotely via HTTP, but just not getting a certificate from Let’s Encrypt.
Fixed it!
In your configuration.yaml file, look at the http: section carefully. If you removed the # to uncomment the section, you may have left behind an extra space. It needs to be all the way to the left with no spaces.
There is no indentation error warning! Everything looks good but the HTTP section does not get implemented.
1 Like
I have the same error after having to replace my sd card. I wonder if Lets Encrypt refuses to issue certificates to a server that it already issued certificates to. My most recent backup did not include the certificates.
JimLei’s fix did not apply to me. No extra spaces in my configuration.yaml.
My certificate expired 2 days ago. I’m having the same issue; DuckDNS addon will not renew the certificate. Tried uninstalling/reinstalling. I get the same error as OP.
Well this is certainly not an isolated problem then it would appear.
I’m pretty sure the error is not in my config. Will definitely double check though.
UPDATE:
Rolling the add-on to 1.6 prevents the add-on from getting the error, and it successfully generates the certificate. I had to disable the nginx add-on before it was working again, but that did fix it.
UPDATE2: Ok. So I disabled the NGINX add-on, then rolled back to 1.6. Then re-enabled NGINX and I’m back in business!
Great, how did you roll back to 1.6 ?
I had a snapshot that contained it; I de-selected the whole snapshot save the duckDNS addon, and restored it.
Is there any other way to install an older version of an addon than by having a snapshot?
I had an issue with another addon and asked the developer this exact question. Answer: nope.
Its a bug with dehydrated in the plugin, if it gets repackaged with the latest version it should start working again.
I manually updated dehydrated in the docker container to run the command to generate the ssl. Its hacky but it worked for a one off, hopefully itll be fixed before I need to regenerate 
Please report the issue:
There is already an issue here https://github.com/home-assistant/hassio-addons/issues/637 which I have added the details to, do you also need one in the main repo?
Nope. That’s perfect.
Can this be done in Hassio, or do you have your docker mounted on another OS and can you access the root files?
The update to 1.8 of the DuckDNS add-on fixed this for me. 
Yep it works now. Back in business!