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
+ Account already registered!
[23:52:51] WARNING:
[23:52:54] INFO: Renew certificate for domains: porat.duckdns.org and aliases:
# INFO: Using main config file /data/workdir/config
Processing porat.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 ###.duckdns.org
+ 1 pending challenge(s)
+ Deploying challenge tokens...
ERROR: deploy_challenge hook returned with non-zero exit code
When you say it started in the last few days, it worked before? I’m a relatively new user and wasn’t sure if I’d made an error in configuration as I’m getting this too.
Yeah, that fixed all my errors I was getting in both NGINX and Duck DNS… amazing how much a little space at the front of that key can mess things up! Thanks for that tip!
Wow unbelievable i spent hours troubleshooting this shit and same exact thing when i saw what you said about the space I checked and I did the same thing haha saved the day
I have installed Duck DNS in January, it was runnung well untill may and now I get this error message : “ERROR: deploy_challenge hook returned with non-zero exit code”
I checked the token : it seems correct. Do you have any other idea ?