3 months ago I was was able to get help on this site ( NGINX - HTTP Challenges Not Passing Due To MIME Types ) I’m now having trouble auto renewing. At the command line in my server I have: deploy@server:/var/www/html$ sudo certbot certonly --webroot -w /var/www/html --agree-tos --email myname@yahoo…

Hi @kc1 , [image] kc1: server { listen 80; server_name example.com www.example.com ; return 301 https:$server_name$request_uri; } You need to fix your redirection, you forgot to add // to https: return 301 https://$server_name$request_uri; This is causing a wrong redirection appending t…

[Capture] Hi guys, Thanks for your help on this. I’m still getting the same error. The screenshot of the letsencrypt system status says operational in the screenshot I just took. heres the output: deploy@server:~$ sudo certbot certonly --webroot -w /var/www/html --agree-tos --email myname@yah…

@kc1 Is that the actual output or did you modify it? Meaning did you replace the actual domain names in the output with example.com , or is that literally what it says? Looks like you might need to modify the command/script for renewing the certs because it’s still using dummy/example data.

I suspected IPv6 initially because a very common issue on the forum when someone has an AAAA record in DNS, but their server is not properly configured to reply to IPv6 requests. Let’s Encrypt will check the IPv6 address first, and can fail there. A change was recently made no Let’s Encrypt that is …

I replaced the domain names with example.com

So are you saying set up a AAAA record?

[image] kc1: So are you saying set up a AAAA record? Adding an AAAA record is unlikely to help. That particular problem is generally about people who have one but whose AAAA record points to a non-working IPv6 address.

Can you let us know the domain name? Feel free to private message if you’d like. Have you 100% confirmed that if you go to your-domain.com/.well-known/acme-challenge/ that it displays the response correctly?

Hi @nschirmer , [image] nschirmer: This URL is a 404 which is the issue. The challenge is deleted by the certbot client so it is normal to receive a 404 error, that is not the problem, as I said, the problem is a wrong redirection reaching the http site (as Let's Encrypt does). The output is…

Got it. Sorry, I use a more manual method rather than having certbot create and delete the challenges, so that part got me. Thanks for chiming in, and hopefully adding the double forward slash helps resolve this for him!

Failure during auto renew

Help

Topic		Replies	Views
Certbot Stuck in the Same Renew Error Help	7	2636	December 12, 2017
Renew failure with certbot or letsencrypt-auto Help	24	7135	June 14, 2017
Certificate Renewal via http-01 webroot Failed authorization procedure Help	2	1331	April 6, 2018
Timeout during connect (likely firewall problem) after changing internet provider Help	40	4506	January 31, 2022
Error getting validation data (http-01) Help	10	15957	July 6, 2017

Failure during auto renew

Related topics