I think I asked a similar question before to this, but I can't find a way of searching my own posts. Anyway, therefore I need to ask again.
I received an email saying
Hello,
Your certificate (or certificates) for the names listed below will expire in 19 days (on 05 Aug 22 21:40 +0000). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors.
We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration. See Integration Guide - Let's Encrypt for details.
Then a lot of domains are listed. Now bitcoinhelp.uk was indeed expired about 2 years ago, but the rest have been recently renewed. As far as I can determine with
https://www.ssllabs.com/ssltest/analyze.html?d=dhars.org.uk
the domain dhars.org.uk does not expire until 1 month and 10 days. So why am I getting emails saying it is about to expire. I have not checked them all, but of those I have checked, with the exception of bitcoinhelp.uk , nothing is due to expire soon.
|Valid from |Sun, 29 May 2022 11:03:10 UTC|
|Valid until |Sat, 27 Aug 2022 11:03:09 UTC (expires in 1 month and 10 days)|
bitcoinhelp.uk
dhars.org.uk
g8wrb.co.uk
kirbymicrowave.co.uk
kirkbymicrowave.co.uk
kirkbymicrowave.com
www.bitcoinhelp.uk
www.dhars.org.uk
www.g8wrb.co.uk
www.kirbymicrowave.co.uk
www.kirkbymicrowave.co.uk
www.kirkbymicrowave.com
1 Like
Rip
July 17, 2022, 2:14am
2
I have looked at your sites. Your certs are good to go. Is it possible that you have added or removed a domain from your cert? This could relate to the email you received . The system doesn't know if you make a change, it only remembers what you requested the last time you renewed. So if your domains are current and your certs are fresh, you might not have to worry about the email.
Hope this helps
7 Likes
Try clicking your name at the top of one of your posts in this thread. Then click your name again on the pop-up that appears. View the Activity tab for all your activity. Also, the Search has an advanced option you can limit to certain posters.
I agree with rip, it looks like all your domains are sending out certs for just their own domain name. You used to get a cert with many names combined. It is this combined cert that is expiring which it doesn't look like you use. So just consider the email a friendly warning.
Perhaps this tool will help you visualize what is happening
https://tools.letsdebug.net/cert-search?m=domain&q=dhars.org.uk&d=2160
8 Likes
Yes, I know what happened there. I did have a certificate that showed bitcoinhelp.co.uk as the main one, with the other 10 or so domains less prominent, which was not what I wanted for my company.. So now I have one certificate per domain, rather than a certificate covering multiple domains.
I would like to avoid the spurious emails, as having them will mean I am likely to miss a more important notification. I assume revoking the certificate is one way, but is there a better way? I would much rather stop the reminders, rather than just ignore them.
2 Likes
Osiris
July 17, 2022, 10:32am
5
It's not possible to unsubscribe from individual certificate expiry notifications.
6 Likes
The particular certificates do not appear to be managed by certbot - they were probably generated on another server, to which I no longer have access. However, I do have a backup, in the form of a tar file, of the directory on the other server. Is there any way I can revoke the certificate, to stop the reminders?
root@foobar:/etc# certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Found the following certs:
Certificate Name: bitcoinhelp.uk
Serial Number: 34fce17f62370e90e3bc2754374f09b805f
Key Type: RSA
Domains: bitcoinhelp.uk www.bitcoinhelp.uk
Expiry Date: 2022-10-15 00:28:25+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/bitcoinhelp.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/bitcoinhelp.uk/privkey.pem
Certificate Name: dell-uk-sales.co.uk
Serial Number: 323622fd0933cd278297a46532f762cc21c
Key Type: RSA
Domains: dell-uk-sales.co.uk www.dell-uk-sales.co.uk
Expiry Date: 2022-08-30 00:25:17+00:00 (VALID: 43 days)
Certificate Path: /etc/letsencrypt/live/dell-uk-sales.co.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/dell-uk-sales.co.uk/privkey.pem
Certificate Name: dhars.org.uk
Serial Number: 30bc6a480ad5c8ccd66915329497d17ab75
Key Type: RSA
Domains: dhars.org.uk www.dhars.org.uk
Expiry Date: 2022-08-27 11:03:09+00:00 (VALID: 40 days)
Certificate Path: /etc/letsencrypt/live/dhars.org.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/dhars.org.uk/privkey.pem
Certificate Name: g8wrb.co.uk
Serial Number: 3e0cd429b7944b48eac9d1aa0216e807722
Key Type: RSA
Domains: g8wrb.co.uk www.g8wrb.co.uk
Expiry Date: 2022-10-05 20:50:59+00:00 (VALID: 80 days)
Certificate Path: /etc/letsencrypt/live/g8wrb.co.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/g8wrb.co.uk/privkey.pem
Certificate Name: kirbymicrowave.co.uk
Serial Number: 444c24c862707aeb33d1b0fec8017c03e69
Key Type: RSA
Domains: kirbymicrowave.co.uk www.kirbymicrowave.co.uk
Expiry Date: 2022-10-05 10:40:30+00:00 (VALID: 79 days)
Certificate Path: /etc/letsencrypt/live/kirbymicrowave.co.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/kirbymicrowave.co.uk/privkey.pem
Certificate Name: kirkbymicrowave.com
Serial Number: 44ec459d549047e275cc5e8bc75f8fa5ccc
Key Type: RSA
Domains: kirkbymicrowave.com www.kirkbymicrowave.com
Expiry Date: 2022-10-05 10:40:41+00:00 (VALID: 79 days)
Certificate Path: /etc/letsencrypt/live/kirkbymicrowave.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/kirkbymicrowave.com/privkey.pem
Certificate Name: www.dhars.org.uk
Serial Number: 3003009b10db925633f1f476aea3758b7cb
Key Type: RSA
Domains: www.dhars.org.uk
Expiry Date: 2022-10-05 10:40:50+00:00 (VALID: 79 days)
Certificate Path: /etc/letsencrypt/live/www.dhars.org.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.dhars.org.uk/privkey.pem
Certificate Name: www.kirkbymicrowave.co.uk
Serial Number: 490cbd9fc88a83ceb3fb48116e5bf4a33a5
Key Type: RSA
Domains: www.kirkbymicrowave.co.uk kirkbymicrowave.co.uk
Expiry Date: 2022-10-05 10:41:00+00:00 (VALID: 79 days)
Certificate Path: /etc/letsencrypt/live/www.kirkbymicrowave.co.uk/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.kirkbymicrowave.co.uk/privkey.pem
Certificate Name: www.rftestkit.com
Serial Number: 31e14c9c798f6b110bf3e17e221a9b69789
Key Type: RSA
Domains: www.rftestkit.com rftestkit.com
Expiry Date: 2022-08-29 09:16:27+00:00 (VALID: 42 days)
Certificate Path: /etc/letsencrypt/live/www.rftestkit.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.rftestkit.com/privkey.pem
1 Like
Osiris
July 17, 2022, 1:00pm
7
If you have the public key then yes, you can revoke the certificate.
5 Likes
Where would I look to find the correct file(s) and how would I revoke them? These are the files I have
root@foobar:/tmp/letsencrypt# find .
.
./renewal-hooks
./renewal-hooks/post
./renewal-hooks/pre
./renewal-hooks/deploy
./.updated-options-ssl-apache-conf-digest.txt
./renewal
./renewal/kirkbymicrowave.co.uk.conf
./renewal/www.bitcoinhelp.uk.conf
./renewal/dhars.org.uk.conf
./renewal/www.g8wrb.co.uk.conf
./renewal/g8wrb.co.uk.conf
./renewal/www.kirkbymicrowave.co.uk.conf
./renewal/kirkbymicrowave.com.conf
./renewal/kirkbymicrowave.com-0001.conf
./renewal/www.kirbymicrowave.co.uk.conf
./renewal/bitcoinhelp.uk.conf
./renewal/kirbymicrowave.co.uk.conf
./renewal/www.dhars.org.uk.conf
./archive
./archive/kirkbymicrowave.com-0001
./archive/kirkbymicrowave.com-0001/chain1.pem
./archive/kirkbymicrowave.com-0001/privkey1.pem
./archive/kirkbymicrowave.com-0001/cert1.pem
./archive/kirkbymicrowave.com-0001/fullchain1.pem
./archive/www.bitcoinhelp.uk
./archive/www.bitcoinhelp.uk/chain1.pem
./archive/www.bitcoinhelp.uk/privkey1.pem
./archive/www.bitcoinhelp.uk/cert1.pem
./archive/www.bitcoinhelp.uk/fullchain1.pem
./archive/kirkbymicrowave.com
./archive/kirkbymicrowave.com/chain1.pem
./archive/kirkbymicrowave.com/privkey1.pem
./archive/kirkbymicrowave.com/cert1.pem
./archive/kirkbymicrowave.com/fullchain1.pem
./archive/bitcoinhelp.uk
./archive/bitcoinhelp.uk/chain1.pem
./archive/bitcoinhelp.uk/privkey1.pem
./archive/bitcoinhelp.uk/cert1.pem
./archive/bitcoinhelp.uk/fullchain1.pem
./archive/www.g8wrb.co.uk
./archive/www.g8wrb.co.uk/chain1.pem
./archive/www.g8wrb.co.uk/privkey1.pem
./archive/www.g8wrb.co.uk/cert1.pem
./archive/www.g8wrb.co.uk/fullchain1.pem
./archive/www.dhars.org.uk
./archive/www.dhars.org.uk/chain1.pem
./archive/www.dhars.org.uk/privkey1.pem
./archive/www.dhars.org.uk/cert1.pem
./archive/www.dhars.org.uk/fullchain1.pem
./archive/www.kirbymicrowave.co.uk
./archive/www.kirbymicrowave.co.uk/chain1.pem
./archive/www.kirbymicrowave.co.uk/privkey1.pem
./archive/www.kirbymicrowave.co.uk/cert1.pem
./archive/www.kirbymicrowave.co.uk/fullchain1.pem
./archive/kirbymicrowave.co.uk
./archive/kirbymicrowave.co.uk/chain1.pem
./archive/kirbymicrowave.co.uk/privkey1.pem
./archive/kirbymicrowave.co.uk/cert1.pem
./archive/kirbymicrowave.co.uk/fullchain1.pem
./archive/g8wrb.co.uk
./archive/g8wrb.co.uk/chain1.pem
./archive/g8wrb.co.uk/privkey1.pem
./archive/g8wrb.co.uk/cert1.pem
./archive/g8wrb.co.uk/fullchain1.pem
./archive/www.kirkbymicrowave.co.uk
./archive/www.kirkbymicrowave.co.uk/chain1.pem
./archive/www.kirkbymicrowave.co.uk/privkey1.pem
./archive/www.kirkbymicrowave.co.uk/cert1.pem
./archive/www.kirkbymicrowave.co.uk/fullchain1.pem
./archive/dhars.org.uk
./archive/dhars.org.uk/chain1.pem
./archive/dhars.org.uk/privkey1.pem
./archive/dhars.org.uk/cert1.pem
./archive/dhars.org.uk/fullchain1.pem
./archive/kirkbymicrowave.co.uk
./archive/kirkbymicrowave.co.uk/chain1.pem
./archive/kirkbymicrowave.co.uk/privkey1.pem
./archive/kirkbymicrowave.co.uk/cert1.pem
./archive/kirkbymicrowave.co.uk/fullchain1.pem
./options-ssl-apache.conf
./csr
./csr/0002_csr-certbot.pem
./csr/0018_csr-certbot.pem
./csr/0000_csr-certbot.pem
./csr/0014_csr-certbot.pem
./csr/0006_csr-certbot.pem
./csr/0004_csr-certbot.pem
./csr/0003_csr-certbot.pem
./csr/0008_csr-certbot.pem
./csr/0021_csr-certbot.pem
./csr/0015_csr-certbot.pem
./csr/0001_csr-certbot.pem
./csr/0007_csr-certbot.pem
./csr/0017_csr-certbot.pem
./csr/0013_csr-certbot.pem
./csr/0005_csr-certbot.pem
./csr/0016_csr-certbot.pem
./csr/0010_csr-certbot.pem
./csr/0019_csr-certbot.pem
./csr/0009_csr-certbot.pem
./csr/0011_csr-certbot.pem
./csr/0020_csr-certbot.pem
./csr/0012_csr-certbot.pem
./accounts
./accounts/acme-v02.api.letsencrypt.org
./accounts/acme-v02.api.letsencrypt.org/directory
./accounts/acme-v02.api.letsencrypt.org/directory/ef3f4b05cf184ff113f870097624dd8f
./accounts/acme-v02.api.letsencrypt.org/directory/ef3f4b05cf184ff113f870097624dd8f/private_key.json
./accounts/acme-v02.api.letsencrypt.org/directory/ef3f4b05cf184ff113f870097624dd8f/regr.json
./accounts/acme-v02.api.letsencrypt.org/directory/ef3f4b05cf184ff113f870097624dd8f/meta.json
./accounts/acme-staging-v02.api.letsencrypt.org
./accounts/acme-staging-v02.api.letsencrypt.org/directory
./accounts/acme-staging-v02.api.letsencrypt.org/directory/8a47ba598e94695aea3959ef8f7993d5
./accounts/acme-staging-v02.api.letsencrypt.org/directory/8a47ba598e94695aea3959ef8f7993d5/private_key.json
./accounts/acme-staging-v02.api.letsencrypt.org/directory/8a47ba598e94695aea3959ef8f7993d5/regr.json
./accounts/acme-staging-v02.api.letsencrypt.org/directory/8a47ba598e94695aea3959ef8f7993d5/meta.json
./keys
./keys/0009_key-certbot.pem
./keys/0017_key-certbot.pem
./keys/0014_key-certbot.pem
./keys/0003_key-certbot.pem
./keys/0011_key-certbot.pem
./keys/0000_key-certbot.pem
./keys/0008_key-certbot.pem
./keys/0004_key-certbot.pem
./keys/0021_key-certbot.pem
./keys/0018_key-certbot.pem
./keys/0020_key-certbot.pem
./keys/0015_key-certbot.pem
./keys/0016_key-certbot.pem
./keys/0013_key-certbot.pem
./keys/0002_key-certbot.pem
./keys/0019_key-certbot.pem
./keys/0012_key-certbot.pem
./keys/0005_key-certbot.pem
./keys/0007_key-certbot.pem
./keys/0006_key-certbot.pem
./keys/0001_key-certbot.pem
./keys/0010_key-certbot.pem
./live
./live/kirkbymicrowave.com-0001
./live/kirkbymicrowave.com-0001/cert.pem
./live/kirkbymicrowave.com-0001/fullchain.pem
./live/kirkbymicrowave.com-0001/README
./live/kirkbymicrowave.com-0001/privkey.pem
./live/kirkbymicrowave.com-0001/chain.pem
./live/www.bitcoinhelp.uk
./live/www.bitcoinhelp.uk/cert.pem
./live/www.bitcoinhelp.uk/fullchain.pem
./live/www.bitcoinhelp.uk/README
./live/www.bitcoinhelp.uk/privkey.pem
./live/www.bitcoinhelp.uk/chain.pem
./live/kirkbymicrowave.com
./live/kirkbymicrowave.com/cert.pem
./live/kirkbymicrowave.com/fullchain.pem
./live/kirkbymicrowave.com/README
./live/kirkbymicrowave.com/privkey.pem
./live/kirkbymicrowave.com/chain.pem
./live/bitcoinhelp.uk
./live/bitcoinhelp.uk/cert.pem
./live/bitcoinhelp.uk/fullchain.pem
./live/bitcoinhelp.uk/README
./live/bitcoinhelp.uk/privkey.pem
./live/bitcoinhelp.uk/chain.pem
./live/www.g8wrb.co.uk
./live/www.g8wrb.co.uk/cert.pem
./live/www.g8wrb.co.uk/fullchain.pem
./live/www.g8wrb.co.uk/README
./live/www.g8wrb.co.uk/privkey.pem
./live/www.g8wrb.co.uk/chain.pem
./live/README
./live/www.dhars.org.uk
./live/www.dhars.org.uk/cert.pem
./live/www.dhars.org.uk/fullchain.pem
./live/www.dhars.org.uk/README
./live/www.dhars.org.uk/privkey.pem
./live/www.dhars.org.uk/chain.pem
./live/www.kirbymicrowave.co.uk
./live/www.kirbymicrowave.co.uk/cert.pem
./live/www.kirbymicrowave.co.uk/fullchain.pem
./live/www.kirbymicrowave.co.uk/README
./live/www.kirbymicrowave.co.uk/privkey.pem
./live/www.kirbymicrowave.co.uk/chain.pem
./live/kirbymicrowave.co.uk
./live/kirbymicrowave.co.uk/cert.pem
./live/kirbymicrowave.co.uk/fullchain.pem
./live/kirbymicrowave.co.uk/README
./live/kirbymicrowave.co.uk/privkey.pem
./live/kirbymicrowave.co.uk/chain.pem
./live/g8wrb.co.uk
./live/g8wrb.co.uk/cert.pem
./live/g8wrb.co.uk/fullchain.pem
./live/g8wrb.co.uk/README
./live/g8wrb.co.uk/privkey.pem
./live/g8wrb.co.uk/chain.pem
./live/www.kirkbymicrowave.co.uk
./live/www.kirkbymicrowave.co.uk/cert.pem
./live/www.kirkbymicrowave.co.uk/fullchain.pem
./live/www.kirkbymicrowave.co.uk/README
./live/www.kirkbymicrowave.co.uk/privkey.pem
./live/www.kirkbymicrowave.co.uk/chain.pem
./live/dhars.org.uk
./live/dhars.org.uk/cert.pem
./live/dhars.org.uk/fullchain.pem
./live/dhars.org.uk/README
./live/dhars.org.uk/privkey.pem
./live/dhars.org.uk/chain.pem
./live/kirkbymicrowave.co.uk
./live/kirkbymicrowave.co.uk/cert.pem
./live/kirkbymicrowave.co.uk/fullchain.pem
./live/kirkbymicrowave.co.uk/README
./live/kirkbymicrowave.co.uk/privkey.pem
./live/kirkbymicrowave.co.uk/chain.pem
1 Like
Osiris
July 17, 2022, 1:15pm
9
In the appropriate /live/
directory.
Please see the Certbot user guide about revoking certificates .
6 Likes
In case you don't know - you only receive 3 emails per cert that you don't renew. They appear 20, 10, and 1 days before expiry . They won't persist forever like some reminder emails from purchased services.
9 Likes
danb35
July 17, 2022, 6:42pm
11
I don't believe revoking the cert will stop the reminders. You'll get a total of three (20 days before expiration, 10 days, and 1 day, IIRC), and then they'll stop, because that cert will be expired. I don't think the juice is worth the squeeze here, particularly with the risk of revoking the wrong cert.
6 Likes
Osiris
July 17, 2022, 6:46pm
12
It will, see the Boulder source:
// sequentially fetch the certificate details. This avoids an expensive
// JOIN.
var serials []string
_, err := m.dbMap.WithContext(ctx).Select(
&serials,
`SELECT
cs.serial
FROM certificateStatus AS cs
WHERE cs.notAfter > :cutoffA
AND cs.notAfter <= :cutoffB
AND cs.status != "revoked"
AND COALESCE(TIMESTAMPDIFF(SECOND, cs.lastExpirationNagSent, cs.notAfter) > :nagCutoff, 1)
ORDER BY cs.notAfter ASC
LIMIT :limit`,
map[string]interface{}{
"cutoffA": left,
"cutoffB": right,
"nagCutoff": expiresIn.Seconds(),
"limit": m.limit,
},
)
8 Likes
system
Closed
August 16, 2022, 6:47pm
13
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.