Cert renewal no longer working with Letsencrypt/DuckDNS on Hass.io

Installation Home Assistant OS
1

I was a couple versions behind. After updating Hassio and DuckDNS, DuckDNS is supposed to renew Letsencrypt certification, but it isn’t. I added “accept_terms”: true. I’m thinking I’ll uninstall both addons and then just reinstall the new DuckDNS to see if that fixes it… unless someone knows a better idea?

2

You don’t need the Letsencrypt add-on since 0.55
I followed this:


Check the DuckDNS log file just after 8:00 AM and you will see a renewal attempt.
The Letsencrypt sensor does not seem compatible with this new method that is totally automatic. No port forwarding changes required!
3

hi,

i when following the steps until this point. I hope somebody can help me out.

Thanks

homeassistant@Home-Theater:~/.homeassistant/dehydrated $ ./dehydrated -c
# INFO: Using main config file /home/homeassistant/.homeassistant/dehydrated/config
Unknown hook set
Processing xxx.duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting challenge for xxx.duckdns.org...
Unknown hook set
 + Responding to challenge for xxx.duckdns.org...
Unknown hook set
Unknown hook set
ERROR: Challenge is invalid! (returned: invalid) (result: {
  "type": "dns-01",
  "status": "invalid",
  "error": {
    "type": "urn:acme:error:unauthorized",
    "detail": "Correct value not found for DNS challenge",
    "status": 403
  },
  "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/vEShG6CpSYhxDoLlY3MapfLf7-U-2DnAUaHOz7Hl2dE/2303038056",
  "token": "long string",
  "keyAuthorization": "long string"
})
4

Your post is not relevant for a hass.io setup of DuckDNS with included Letsencrypt.