My domain is: lyft.ir I ran this command: sudo certbot renew It produced this output: The following errors were reported by the server: Domain: lyft.ir Type: unauthorized Detail: Invalid response from https://lyft.ir/.well-known/acme-challenge/rdV6k440gSQegFp1uR0A0mP3ZEoNnKNkrpc2JV4K1qM [2…

[image] _az: cat /etc/letsencrypt/renewal/lyft.ir.conf renew_before_expiry = 30 days version = 0.28.0 archive_dir = /etc/letsencrypt/archive/lyft.ir cert = /etc/letsencrypt/live/lyft.ir/cert.pem privkey = /etc/letsencrypt/live/lyft.ir/privkey.pem chain = /etc/letsencrypt/live/lyft.ir/chai…

This is a common issue with Cloudflare CDN and Certbot’s nginx plugin: Certbot sets up the challenge response on your server’s port 80 virtualhost only. Cloudflare causes all traffic between Cloudflare and your server to be secured with HTTPS. This means that the challenge response rule never gets …

Thanks for your response dear. But I already tried that (I created the exactly same directory ‘/var/www/html/.well-known/acme-challenge’) and I tested it by putting a test.html file in there. https://lyft.ir/.well-known/acme-challenge/test.html So you think that the problem might be because of the …

That 301 is fine. I don’t think Cloudflare even hits it, because it probably goes directly to HTTPS when speaking to the origin. My response had two parts - you also need to tell Certbot to use the webroot authenticator instead. The nginx authenticator does not use your webroot. So try: certbot r…

This is the result: Attempting to renew cert (lyft.ir) from /etc/letsencrypt/renewal/lyft.ir.conf produced an unexpected error: The requested weboot plugin does not appear to be installed. Skipping.

Sorry, that’s my fault, a typo. It should be webroot not weboot.

The fault is mine my friend. I should have checked it. And thanks. It worked. But I really didn’t get the point and the root of the problem :smile: Is it because --dry-run ?

--dry-run is just for testing. You should get rid of it and run the command without it. What we changed was that we changed from the “nginx authenticator” to the “webroot authenticator” - it causes Certbot to perform the domain validation a little bit differently. The root of the problem is an inc…

Wow. well, thanks. You saved my life :sunflower: :heart:

Acme challenge file not found

Help

_az July 28, 2019, 8:47am 2

What authenticator are you using?

cat /etc/letsencrypt/renewal/lyft.ir.conf

Topic		Replies	Views
Unable to renew certs, Invalid response from well-known acme-challenge 404 Help	8	1823	March 9, 2023
Error for renewing certbot Help	12	2426	September 27, 2019
Unable to renew lets encrypt certificate Help	4	699	January 21, 2021
Certbot renew error -- Invalid response from Help	6	11145	November 3, 2018
Certbot Renew Failure: Invalid Response Help	6	216	January 12, 2025

Acme challenge file not found

Related topics