#DuckDNS update broke wildcard certs

1 messages · Page 1 of 1 (latest)

young urchin
#

I upgraded to 1.23.0 and now my HASS is broken because when renewing the letsencrypt cert (duckdns does the renewing not the letsencrypt add-on) it only now gives me MYDOMAIN.duckdns.org instead of *.MYDOMAIN.duckdns.org. Others are reporting this also: https://github.com/home-assistant/addons/issues/4111#issuecomment-3180239334

There were no config changes. How can I downgrade duckDNS to an earlier version easily? I do not have the "add-on downgrade backup" ... I should have clicked that button <sad_face>

GitHub
[DuckDNS] 400 error when renewing certs: challenge is invalid · Is...

Describe the issue you are experiencing Hello, I’ve noticed DuckDNS is failing to renew my certificate. I have no idea why it’s giving that error message, but it seems like it might be tied to rece...

#

Here's my config ```domains:

  • "*.MYDOMAIN.duckdns.org > MYDOMAIN.duckdns.org"
    token: [redacted]
    aliases: []
    lets_encrypt:
    accept_terms: true
    algo: secp384r1
    certfile: fullchain.pem
    keyfile: privkey.pem
    seconds: 300```
young urchin
#

They released a new update !!! Still broken <sad face>

young urchin
#

FYI for those following on, someone has an open PR to fix this