I am trying to setup remote access using the speak to the geek video, but have fallen at the first hurdle.
I have created a duckdns.org domain and installed duckdns add-on. But when I fill in the config and try to start the add-on I just get the spinning circle for quite a while and it doesn’t start.
this is the log
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
INFO: Using main config file /data/workdir/config
- Generating account key…
- Registering account key with ACME server…
- Fetching account URL…
- Done!
[09:51:20] WARNING: KO
[09:51:20] INFO: Renew certificate for domains: xxxxxxxx…duckdns.org and aliases:
INFO: Using main config file /data/workdir/config
- Creating chain cache directory /data/workdir/chains
Processing xxxxxxxx…duckdns.org - Creating new directory /data/letsencrypt/xxxxxxxx…duckdns.org …
- Signing domains…
- Generating private key…
- Generating signing request…
- Requesting new certificate order from CA…
- Received 1 authorizations URLs from the CA
- Handling authorization for xxxxxxxx…duckdns.org
- 1 pending challenge(s)
- Deploying challenge tokens…
OK + Responding to challenge for xxxxxxxx…duckdns.org authorization… - Challenge is valid!
- Cleaning challenge tokens…
OK + Requesting certificate… - Checking certificate…
- Done!
- Creating fullchain.pem…
- Done!
[09:56:36] WARNING: KO
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
INFO: Using main config file /data/workdir/config
- Generating account key…
- Registering account key with ACME server…
- Fetching account URL…
- Done!
[10:03:21] INFO: Renew certificate for domains: xxxxxxxx…duckdns.org and aliases:
INFO: Using main config file /data/workdir/config
- Creating chain cache directory /data/workdir/chains
Processing xxxxxxxx…duckdns.org - Creating new directory /data/letsencrypt/xxxxxxxx…duckdns.org …
- Signing domains…
- Generating private key…
- Generating signing request…
- Requesting new certificate order from CA…
- Received 1 authorizations URLs from the CA
- Handling authorization for xxxxxxxx.duckdns.org
- 1 pending challenge(s)
- Deploying challenge tokens…
OK + Responding to challenge for wavydavy.duckdns.org authorization… - Cleaning challenge tokens…
OK + Challenge validation has failed
ERROR: Challenge is invalid! (returned: invalid) (result: [“type”] “dns-01”
[“status”] “invalid”
[“error”,“type”] “urn:ietf:params:acme:error:unauthorized”
[“error”,“detail”] “During secondary validation: Incorrect TXT record "" found at _acme-challenge.xxxxxxxx…duckdns.org”
[“error”,“status”] 403
[“error”] {“type”:“urn:ietf:params:acme:error:unauthorized”,“detail”:“During secondary validation: Incorrect TXT record "" found at _acme-challenge.xxxxxxxx…duckdns.org”,“status”:403}
[“url”] “https://acme-v02.api.letsencrypt.org/acme/chall-v3/350178768387/BlhKHQ”
[“token”] “PYsgw6W3OLdbtZmQd0jhZddXboaOWogoJrsTeiP0w8c”
[“validationRecord”,0,“hostname”] “xxxxxxxx…duckdns.org”
[“validationRecord”,0] {“hostname”:“xxxxxxxx…duckdns.org”}
[“validationRecord”] [{“hostname”:“xxxxxxxx.duckdns.org”}]
[“validated”] “2024-05-13T09:03:30Z”)