Duckdns troubles on hassio

Installation Home Assistant OS
1

Receive this error in log???

starting version 3.2.2
# INFO: Using main config file /data/workdir/config
+ Account already registered!
Sat Oct  7 10:07:15 CEST 2017: KO
# INFO: Using main config file /data/workdir/config
Processing xxx.duckdns.com
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting challenge for xxx.duckdns.com...
KO + Responding to challenge for xxx.duckdns.com...
KOUnknown hook invalid_challenge
ERROR: Challenge is invalid! (returned: invalid) (result: {
  "type": "dns-01",
  "status": "invalid",
  "error": {
    "type": "urn:acme:error:unauthorized",
    "detail": "No TXT records found for DNS challenge",
    "status": 403
  },
  "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/Wfecv24KfV7-kwZtcLwT3A-utEsyJqOTDIuo_DM-PDo/2148829998",
  "token": "fwmh4d4t8nKWaEGx2bwCpD1LTPPZt0tGgjOItFJ5d_E",
  "keyAuthorization": "fwmh4d4t8nKWaEGx2bwCpD1LTPPZt0tGgjOItFJ5d_E.RonXQX7jKLjkfUjzIn417ainOKrB_Z_mFsyW3jJV-k0"
})
2

my options are

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "kjhlkjhkljhblkjhblkjhblkhjblkhjgblkhjgbn",
  "domains": [
    "xxx.duckdns.com"
  ],
  "seconds": 300
}
3

It’s .org mate :slight_smile:

4

Yes I then changed it, but still not working

5

This is letsencypt
{
“challenge”: “https”,
“email”: “[email protected]”,
“domains”: [
“xxx.duckdns.org”
],
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

This duckdns
{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “3a21aa6c-xxx-49a4-aba3-xxx”,
“domains”: [
“xxx.duckdns.org”
],
“seconds”: 300
}

6

Check my original thread that you also posted in.

7

Which one, I posted in many

8

Duckdns starts ok, letsencrypt does not start in hassio