# Could not renew Let's Encrypt certificates **URL:** \ **Category:** Help\ **Created:** [January 17, 2020, 10:47am UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855 "2020-01-17T10:47:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dc-maruri](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@dc-maruri](https://community.letsencrypt.org/u/dc-maruri)\ **Post date:** [January 17, 2020, 10:47am UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855/1 "2020-01-17T10:47:52Z")
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. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help. My domain is: lauroikastola.eus I ran this command: It produced this output: Could not renew Let’s Encrypt certificates for Agurtzane Mentxaka (login admin). Please log in to Plesk and renew the certificates listed below manually. Renewal of the following Let’s Encrypt certificates has failed: - ‘Lets Encrypt lauroikastola.eus’ [days to expire: 19] lauroikastola.eus The following Let’s Encrypt certificates have been renewed without some of their Subject Alternative Names: My web server is (include version): The operating system my web server runs on is (include version): Debian 8.11 My hosting provider, if applicable, is: OVH I can login to a root shell on my machine (yes or no, or I don’t know): YES I’m using a control panel to manage my site (no, or provide the name and version of the control panel): PLESK 17.8.11 The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): Plesk Let’s Script extension versión 2.8.4-547 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [January 17, 2020, 11:02am UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855/2 "2020-01-17T11:02:39Z")
Hi @dc-maruri > [@dc-maruri](#): > > My domain is: > > lauroikastola.eus looks like you have found a solution. Or you use a completely wrong command. Checking your domain there is a new certificate - [https://check-your-website.server-daten.de/?q=lauroikastola.eus](https://check-your-website.server-daten.de/?q=lauroikastola.eus) ```nohighlight CN=lauroikastola.eus 16.01.2020 15.04.2020 expires in 89 days lauroikastola.eus, www.lauroikastola.eus - 2 entries ``` If you use Plesk, use **only** Plesk, nothing else. Your site isn't perfect (Grade E), but both connections (non-www and www) are secure. And you have already created 4 identical certificates: | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | | Let's Encrypt Authority X3 | 2020-01-15 | 2020-04-14 | lauroikastola.eus, www.lauroikastola.eus | | | | 2 entries | duplicate nr. 4 | | | | | | Let's Encrypt Authority X3 | 2020-01-15 | 2020-04-14 | lauroikastola.eus, www.lauroikastola.eus | | | | 2 entries | duplicate nr. 3 | | | | | | Let's Encrypt Authority X3 | 2020-01-14 | 2020-04-13 | lauroikastola.eus, www.lauroikastola.eus | | | | 2 entries | duplicate nr. 2 | | | | | | Let's Encrypt Authority X3 | 2020-01-14 | 2020-04-13 | lauroikastola.eus, www.lauroikastola.eus | | | | 2 entries | duplicate nr. 1 | | | | | | Let's Encrypt Authority X3 | 2020-01-10 | 2020-04-09 | lauroikastola.eus, www.lauroikastola.eus | | | | 2 entries | | | | | | ---
**Author:** ![dc-maruri](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@dc-maruri](https://community.letsencrypt.org/u/dc-maruri)\ **Post date:** [January 17, 2020, 11:16am UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855/3 "2020-01-17T11:16:02Z")
Thanks JuergenAuer, so we don’t need to worry about the Let’s Script message we receive each day about the “Could not renew Let’s Encrypt certificates” ? We only have used the Let’s Script plesk extension. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [January 17, 2020, 2:24pm UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855/4 "2020-01-17T14:24:47Z")
> [@dc-maruri](#): > > so we don’t need to worry about the Let’s Script message we receive each day about the “Could not renew Let’s Encrypt certificates” ? I don't know. But Letsencrypt doesn't send daily mails. Read > **[Expiration Emails - Let's Encrypt](https://letsencrypt.org/docs/expiration-emails/)** > > Subscribing If you provide an email address to Let’s Encrypt when you create your account, we’ll do our best to automatically send you expiry notices when your certificate is coming up for renewal. We try to send the first notice at 20... PS: Sometimes users change their hoster. And the old system sends such mails. So check the header to find the ip of the sender and check, if this is your current system. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [February 16, 2020, 2:26pm UTC](https://community.letsencrypt.org/t/could-not-renew-lets-encrypt-certificates/110855/5 "2020-02-16T14:26:59Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.