Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com ), so withholding your domain name here does not increase secrecy, but …

@migfilg Sorry about this problem. I don't know why that happened. But, we can get your Apache working again (hopefully) with this change In this file: /etc/httpd/conf.d/vhosts-le-ssl.conf: Inside the VirtualHost section that starts <VirtualHost\ :443> ServerName rdvrsgcl.atractor.pt Change t…

Euh, the fact you were getting that question means you already had a perfectly fine certificate and there was no actual need to replace it.

I was replacing it because it would expire soon and I am not sure if it would be renewed automatically. For this I am using an entry in the crontab, but I just saw that certbot can do that and will be reading User Guide — Certbot 4.0.0.dev0 documentation for instructions.

[image] migfilg: I was replacing it because it would expire soon and I am not sure if would be renewed automatically. If it was due for renewal, you wouldn't have gotten that specific question. The certificate issued today ( crt.sh | 17668181528 ) was a renewal for crt.sh | 17094710039 which d…

In fact the crontab entry was created by me when we started to use these certificates some years ago. I am not an expert in these matters and tried to avoid problems by using means I am used to.

[image] Osiris: The certificate issued today ( crt.sh | 17668181528 ) was a renewal for crt.sh | 17094710039 which due to expire 2025-05-08 which is 32 days into the future Also interesting is that cert with 3 domains name in it is not the one being used for requests to any of those domains. I…

[image] MikeMcQ: @migfilg It looks like you have extra cert(s) that you don't need. If you want help cleaning that up start by showing us output of sudo certbot certificates Yes and thanks! Here is the result: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - …

Thanks. I think having a cert for each VirtualHost in your Apache is easier to maintain. And, we can tell from which cert is being used by each domain that is how you have it setup now. That is good and the "older" cert with all 3 names is probably not needed anymore. So, unless you use the cert …

Thanks for your directions! So, unless you use the cert with all 3 names in it somewhere other than Apache you could sudo certbot delete --cert-name atractor.pt This worked ok after confirmation... After that you can test the automated renew with: sudo certbot renew --dry-run This --dry-run wi…

[image] migfilg: Any help will be most appreciated! @MikeMcQ I think you had the incorrect certificate name in the suggested command :wink:

Yes, it would seem so. Except their system never returned the certificate that used three names. I don't know how that mix up could have happened. I don't have a lot of time right at the moment but will look at it further as soon as I can. Otherwise some manual changes to the Apache config should ge…

Certbot fails to renew certificates

Help

Topic		Replies	Views
Invalid response Help	9	527	March 25, 2023
Certbot wont renew my cert --> 404 Help	40	1084	January 20, 2023
Where are all references to my domain name? Help	24	627	June 19, 2024
All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/fullchain.pem (failure) Help	6	24392	February 1, 2019
No Renew after setup redirect to https Help	20	1618	December 30, 2020

Certbot fails to renew certificates

Related topics