Closed haldi4803 closed 7 months ago
pip install --upgrade certbot==2.1.0 certbot-dns-godaddy
pip install --upgrade certbot==2.1.0 certbot-dns-godaddy
`CommandError: ERROR: Could not find a version that satisfies the requirement certbot-dns-godaddy==2.1.0 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 2.6.0, 2.7.4, 2.8.0) ERROR: No matching distribution found for certbot-dns-godaddy==2.1.0
[notice] A new release of pip is available: 23.3.2 -> 24.0 [notice] To update, run: pip install --upgrade pip
at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)`
so i upgraded tot pip 24 and godaddy DNS script to 2.8.0
AND IT WORKS.. Thank you!
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug Can't issue a wildcard certificate with Let's encrypt on goDaddy.
Nginx Proxy Manager Version V2.11.1
To Reproduce Steps to reproduce the behavior: Create a new Wildcard SSL Certificate with DNS on goDaddy.com
Expected behavior Certificate works. The strange thing is, it DID work few days ago! But then i had some issues with broken certificates missing npm-12 folder and had to delete all, so i ran into Let's encrypt "maximum certificates used" limit. I could create normal Let's Encrypt certificates just fine 5 minutes ago. But Wildcard with DNS challenge doesn't work.
Error in Web Interface
CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.
and here we go with the log to /tmp/letsencrypt-log/letsencrypt.log
changed domain.com to domain.com for saftey... and edited some payloads with *** but that shouldn't matter should it?
The only thing i can read from those logs is this part: Certbot failed to authenticate some domains (authenticator: dns-godaddy). The Certificate Authority reported these problems: Domain: domain.com Type: unauthorized Detail: No TXT record found at _acme-challenge.domain.com
But i'm pretty sure the API key works, as i'm using them as well in OpenWRT DDNS script to change my IP.
Edit:
curl -X GET -H "Authorization: sso-key [API_KEY]:[API_SECRET]" "https://api.godaddy.com/v1/domains/available?domain=example.guru"
Works, so API key is not an issue! {"available":false,"definitive":true,"domain":"domain.com"}Operating System docker on OpenWRT 23.05.0
Additional Info
PATH=/opt/certbot/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt OPENRESTY_VERSION=1.21.4.3 CROWDSEC_OPENRESTY_BOUNCER_VERSION=0.1.7 CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt SUPPRESS_NO_CONFIG_WARNING=1 S6_BEHAVIOUR_IF_STAGE2_FAILS=1 S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0 S6_FIX_ATTRS_HIDDEN=1 S6_KILL_FINISH_MAXTIME=10000 S6_VERBOSITY=1 NODE_ENV=production NPM_BUILD_VERSION=2.11.1 NPM_BUILD_COMMIT=aec3020 NPM_BUILD_DATE=2024-01-21 11:23:57 UTC NODE_OPTIONS=--openssl-legacy-provider