Please fill out the fields below so we can help you better.
My domain is: www.mol.pl
I ran this command: /root/certbot/certbot-auto renew
It produced this output:
The following certs are not due for renewal yet:
/etc/letsencrypt/live/mol.pl/fullchain.pem (skipped)
No renewals were attempted.
Cert not yet due for renewal
My web server is (include version): Apache 2/Centos
I also check my certificate date server side like so:
That gives me date 2017-08-22 which is consistent with what my browser (Firefox) says for the website certificate.
Yet I received an e-mail saying:
Hello,
Your certificate (or certificates) for the names listed below will expire in
19 days (on 23 Jul 17 09:40 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
Your current certificate adds one new name (next.mol.pl), so the email system considers it different, and doesn’t count it as a “renewal”. You and i know that the new certificate replaced the old one, but it doesn’t understand that.
So, you don’t have to do anything. (Unless you have the older certificate installed on a different computer or something.) You can ignore the warning emails about that certificate.
Oh. So that’s the problem. Would be nice if it cloud notice that more recent certificate overlaps the previous one. Shouldn’t be that hard to check DNS list.
Or maybe there is a way to invalidate old certificate manually so that next time the bot don’t send those scary messages ;-)?
(Unless you have the older certificate installed on a different computer or something.) You can ignore the warning emails about that certificate.