Let's Encrypt add-on: DNS challenge with Duck DNS

Installation Home Assistant OS
1

I am considering moving from Home Assistant Core (i.e. Home Assistant on Raspbian) to Home Assistant (i.e. Hassio). In my current setup, I use Duck DNS and Let’s Encrypt via Dehydrated script as described here:
https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt

In this setup, there is no need for to forward port 80 since one can use a DNS challenge (“DNS-01”) that works directly with Duck DNS. However, if I move to Home Assistant (Hassio), it appears that the Let’s Encrypt add-on requires one additional “supported DNS provider” for the DNS challenge as described here: https://github.com/home-assistant/hassio-addons/blob/4e16b62970089c6b50fc14a0ecd21f8095055e89/letsencrypt/DOCS.md

Anyone that can point me in the right direction on how to set up the Let’s Encrypt add-on with a DNS challenge? Which DNS provider should I choose and will it work with Duck DNS? I do not have a registred domain; have been using Duck DNS instead.

Thankful for any ideas or pointers.

2

Use your duckdns domain.

Add that per the config options as described in the docs. Set accept terms to true and start the addon. Its takes care of everything from there. The certs will be created by the duckDNS addon through lets encrypt.

No open ports required for the cert to process.

3

Oh, I thought the Let’s encrypt add-on was needed also. Apparently not :slight_smile: Seems to be working fine now, thanks a lot!

If anyone else is reading, don’t forget that you have to add the certs in the http section of configuration.yaml to get https working.

4

I know this is a little old, I have duckdns running, per the setup, but it is not creating the certs. My /ssl folder is empty.

What do?