hello - i apologize for asking what is probably an obvious question, but i cannot figure out what i might need to do with the fullchain.pem file. here is how my apache httpd.conf looks: SSLCertificateFile /etc/letsencrypt/live/MYDOMAIN.com/cert.pem SSLCertificateKeyFile /etc/letsencrypt…

Staging server flakiness has been addressed by the Let's Encrypt staff. Please try again when you can and report back to us.

is it possible for me to email you a zip file of the results?

You can. Or you can just PM me the results if you wish. We can carry this into the PM to prevent exposure.

[image] edwardsmarkf: same: The following simulated renewals failed: /etc/letsencrypt/live/MYDOMAIN.COM/fullchain.pem (failure) Please paste the entire output so we can see what the actual reported error by the ACME server is. Just knowing it failed leaves too much room for guessing and i…

update: i selected just one of the domain names and did: certbot --apache certonly --dry-run --domains MYDOMAINNAME.COM ; that was successful.:grin: IMPORTANT NOTES: - The dry run was successful. occasionally i get this message back: Failed to renew certificate MYDOMAINNAME.COM with…

Are the ones that are failing consistent or random? Are you seeing the same type of error as before or something different? As Osiris mentioned, knowing the exact error sent by Let's Encrypt, as opposed to the ACME client's interpretation of it, is very helpful.

it's very random. i see notices like this: # certbot --apache renew --dry-run ; Processing /etc/letsencrypt/renewal/MYDOMAIN.com.conf Cert not due for renewal, but simulating renewal for dry run Plugins selected: Authenticator apache, Installer apache Simulating renewal of an existing …

I can't say that I'm really familiar with that error. I'll give time for someone who might have specific knowledge to respond. If no one with specific knowledge responds to provide assistance, I'll start an inquiry.

thank you Griffin. i did try certbot remove; and recreating one of them thinking that might fix it, but that did not solve the issue. maybe i will set up a crontab to run it at 1AM or so & see if the results are different.

I'm slightly confused as to where you might still be using the fullchain.pem file... or are you? [as your apache is version 2.4.6 it can't handle such a file] If you add -vv [or -vvv] to the certbot renewal command line, we might see more detail and better understand the problem.

[image] rg305: I'm slightly confused as to where you might still be using the fullchain.pem file... or are you? [as your apache is version 2.4.6 it can't handle such a file] only slightly confused? wow you are doing much better than i am. now, if you realy want confusing: when i look at t…

Dry-run error messages

Help

griffin February 21, 2021, 6:23pm 24

I've made an inquiry regarding the errors you're seeing:

Topic		Replies	Views
Certbot renew problem Help	28	6387	October 20, 2017
Certbot with Apache - New Certificates Obtained but Apache Not Restarted So They Are Not in Use Help	10	4420	June 1, 2017
All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/fullchain.pem (failure) Help	6	24344	February 1, 2019
How to force Apache 2.4 (httpd) to read fullchain.pem? certbot seems to work but I have an https:// issue X86_64 GNU/Linux (Linux 2 AMI) Help	65	6796	May 2, 2021
Certbot failed to authenticate some domains Help	15	418	April 30, 2024

Dry-run error messages

Related topics