Skip to content

Renewing SSL cert using digitalocean DNS challenge fails #860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
the-holger opened this issue Feb 3, 2021 · 1 comment · Fixed by #1286
Closed

Renewing SSL cert using digitalocean DNS challenge fails #860

the-holger opened this issue Feb 3, 2021 · 1 comment · Fixed by #1286
Labels

Comments

@the-holger
Copy link

I have a setup using the digitalocean DNS challenge to get SSL certs from letsencrypt, specifically a wildcard cert for my domain, which is only available when using the DNS challenge.

I could generate the cert using nginx-proxy-manager without any problems, however I couldn't renew the certs. The webui just gives me a "timeout" error, in the docker logs for the container I found the following:

[2/3/2021] [8:58:38 AM] [SSL      ] › ✖  error     Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation  
Renewal configuration file /etc/letsencrypt/renewal/npm-2.conf (cert: npm-2) produced an unexpected error: 'Namespace' object has no attribute 'dns_digitalocean_credentials'. Skipping.
0 renew failure(s), 1 parse failure(s)
    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:314:20)
    at maybeClose (internal/child_process.js:1051:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

I have absolutely no idea where to start debugging, as the issuing of the certificate was no problem at all. Any help would be really appreciated!

@the-holger the-holger added the bug label Feb 3, 2021
@chaptergy
Copy link
Collaborator

chaptergy commented May 9, 2021

Does your issue still persist?
Could you add what the content of your configuration file /etc/letsencrypt/renewal/npm-2.conf is? Does it by any chance include any line with standalone_supported_challenges? (See this certbot issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants