-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
no longer work with subdomain cert generation #56
Comments
I'm also having this problem, 404 with the subdomain |
Broken in #52 You can pin to the previous version until this is resolved: #52 (comment) |
yes, I have workaround it with this image tag |
Workaround for pip instalation: |
I just opened a new issue without reading this one. Apologies. The issue still persists. I have validated that @blackjackyau image tag does work. Any chance we can get this into the next build? |
believed this is cased by the recent refactoring work "refactor: use the new Lexicon-based plugin API"
certbot certonly \ --authenticator dns-godaddy \ --dns-godaddy-propagation-seconds 120 \ --dns-godaddy-credentials c.ini \ --keep-until-expiring --non-interactive --expand \ --server https://acme-v02.api.letsencrypt.org/directory \ --agree-tos --email ${{ secrets.EMAIL }} \ -d subdomain.domain.com
The request for domain cert will be rejected with error message
Requesting a certificate for subdomain.domain.com Error determining zone identifier for subdomain.domain.com: 404 Client Error: Not Found for url: https://api.godaddy.com/v1/domains/subdomain.domain.com. Ask for help or search for solutions at https://community.letsencrypt.org./ See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
The text was updated successfully, but these errors were encountered: