We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Certbot started to fail suddenly after years of working without problems. If i disable badbot blocker, certbot works as expected.
Domain: xxxxx Type: unauthorized Detail: xx.xx.xx.xx: Invalid response from https://xxxxx/.well-known/acme-challenge/xxxx
I guess the IP of the certbot servers are somehow blocked...
Probably linked to this? https://community.letsencrypt.org/t/unexpected-renewal-failures-since-april-2024-please-read-this/216830
The text was updated successfully, but these errors were encountered:
I've seen this also.
My solution was to comment out this line in conf.d/botblocker-nginx-settings.conf: server_names_hash_bucket_size 256;
server_names_hash_bucket_size 256;
Sorry, something went wrong.
@numediawebsites do we need to uncomment this line after certbot renewal?
mitchellkrogza
No branches or pull requests
Certbot started to fail suddenly after years of working without problems. If i disable badbot blocker, certbot works as expected.
I guess the IP of the certbot servers are somehow blocked...
Probably linked to this?
https://community.letsencrypt.org/t/unexpected-renewal-failures-since-april-2024-please-read-this/216830
The text was updated successfully, but these errors were encountered: