Issue with Duckdns and letsencrypt

Configuration
1

Hello,
I have my old system working with duckdns and letsencrypt separatly.
With this set-up I need to portforward pårt 80 for cert update. It has been working for years but I tend to forgett to update. I want now ti use letsencrypt in Duckdns so I renamed the PEM-files to PE_ in /ssl.
Accepted the letsencrypt in Duckdns and the token is OK.

Still I get:

Processing domain: mydomain .duckdns.org

Terminated

ERROR: deploy_challenge hook returned with non-zero exit code

Processing domain: mydomain .duckdns.org

Terminated

ERROR: deploy_challenge hook returned with non-zero exit code
Any ideas?
I setted up a completly new system with same issue…

2

Did you delete the old domain registered at DuckDNS?

I’m not sure but maybe they only allow one domain per ip address.

3

Hello,
No I used the same duckdns. Only thing I did was to rename the PEM-files in /ssl directory. The DNS lookup is fine, it is only the certificates that does not get renewed from Letsencrypt.
I get the error message

ERROR: deploy_challenge hook returned with non-zero exit code
The only thing I want to acomplish is to not need to use Letsencrypt manually every now and then and have port 80 forwarded.
In another HA I have set up the system and there it works, but here I did not have any certificates at all to start with, So how can I migrate from stand-alone to built-in letsencrypt in duckdns… that is the question…

4

Why did you say this then?

5

Hello,
In my “old” system I am using same duckdns.org domain name as I did with separate duckdns and letsencrypt add-on as I try with the internal letsencrypt (that failes).
On my “new” system I have a new domain connected to another duckdns.org account, I setted up this system from scratch and now the internal letsencrypt works fine. I have same config in both apart from domain and token of course.
I hope this makes it more clear… sorry…

6

Tried again.
Deletet /ssl files, Activated internal letsencrypt in duckdns and hd to remove http: ssl config in configuration.yaml.
and rebooted the NUC, same issue.
Logs as per restart of duckdns:

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service duckdns: stopping

[14:39:48] INFO: Service duckdns exited with code 256 (by signal 15)

s6-rc: info: service duckdns 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

OK

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 duckdns: starting

s6-rc: info: service duckdns 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

+ Account already registered!

[14:39:52] INFO: Starting DuckDNS...

[14:39:53] INFO: Renew certificate for domains: mydomain.duckdns.org and aliases:

# INFO: Using main config file /data/workdir/config

Processing mydomain.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 mydomain.duckdns.org

+ 1 pending challenge(s)

+ Processing each challenge individually...

Processing domain: mydomain.duckdns.org

Terminated

ERROR: deploy_challenge hook returned with non-zero exit code

It takes a couple of minutes until error message pops up, so it’s almost like a timeout…

7

So two duckDNS accounts trying to use the one IP address. This could be your issue. Delete the old account and try again.

8

Hello,
No, they are on separate networks, different WAN’s.
One in my house and one in my friends. In his house he made a duckdns account with his email, we setted it up with duckdns add-on and the internal Letsencrypt.
Since I have an old system with Letsencrypt separatly I just want to have the same but as said it will not update my certificates.
I cannot see any difference between the two configs and that is what is so frustrating…