DuckDNS Addon cannot create wildcard certificate

[JAAlperin]

{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"domains": [
"xxx.duckdns.org",
"*.xxx.duckdns.org"
],
"seconds": 1800
}

results in this:

OKOKOKOK + Responding to challenge for xxx.duckdns.org authorization...

• Cleaning challenge tokens...
  OKOKOKOK + Challenge validation has failed :(
  ERROR: Challenge is invalid! (returned: invalid) (result: {
  "type": "dns-01",
  "status": "invalid",
  "error": {
  "type": "urn:ietf:params:acme:error:unauthorized",
  "detail": "Incorrect TXT record "gYvyuKSEz-Sa58khnK9KUc0MUu3C5WDf_7qRDwlDAcM" found at _acme-challenge.xxx.duckdns.org",
  "status": 403
  },
  "url": "https://acme-v02.api.letsencrypt.org/acme/challenge/szX3vuPHMvfMYF-heQcbgmGA4sYZzSVXMMLbjhDm3_Q/5197664255",
  "token": "MxeILOKZ8GYrxuHkWPQYTu3_ZXjbexpDp_miok76grY"
  })

If I understand the many internet posts regarding this issue, it has to do with HOOK_CHAIN=yes, the tokens in the single TXT record, and has been fixed already in certbot via a changed script.

[metbril]

This issue is not related to the documentation website, so it should be moved to the appropriate one or closed and be re-issued there.

[JAAlperin]

Sorry, Robert. Please be kind enough to point me to the correct place.

Robert ***@***.***> June 20, 2018 at 1:34 AM This issue is not related to the documentation website, so it should be moved to the appropriate one or closed and be re-issued there. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5574 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZEOGmFCGa_eLeNNPkKjvyiTevLeTVZ2ks5t-d7ngaJpZM4Ut7LP>.

Regards, Jeff Alperin H: 561-666-7789 C: 561-797-9876 "It's not rocket surgery!" - Oscar Leroy "You know my rule about circus music!" - Lacey Burroughs

[ghost]

This issue was moved by frenck to home-assistant/addons/issues/336.