• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Letsencrypt monthly renew

Marc77

New Pleskian
Hi,

with letsencrypt a certificate has to be renewd within 3 months. Plesk do this job monthly. Is it possible to change it from 1 month to 2 month or 3 month?

Reason is, that I have to manully add this certificate to my cdn provider and 1 month is a bit short.

Thanks
 
Hi Marc77,

with letsencrypt a certificate has to be renewd within 3 months. Plesk do this job monthly. Is it possible to change it from 1 month to 2 month or 3 month?
it IS possible, but not recommended ( reason will follow below as additional information ).

=> Home > Tools & Settings > Scheduled Tasks > (name of the task ) Extension letsencrypt


Additional information:


Pls. keep in mind the following situation:

domainA.com => Let's Encrypt certificate issued => 01.01.2017, first available renew => 60 days after issuing day => 01.03.2017 => expire date: 31.03.2017
domainB.com => Let's Encrypt certificate issued => 01.02.2017, first available renew => 60 days after issuing day => 01.04.2017 => expire date: 31.04.2017
domainC.com => Let's Encrypt certificate issued => 01.03.2017, first available renew => 60 days after issuing day => 30.04.2017 => expire date: 29.05.2017

Task scheduled to:

01.03.2017
(01.04.2017)
01.05.2017
(01.06.2017)
01.07.2017

Let's Encrypt task: Scheduled every first day of the month will cover each possible renewing day of the three certificates, while a scheduled task of 2 months for example will not cover all first possible renew dates. ;)
 
Last edited by a moderator:
Ok, thank you very much for the detailed explanation. I see the problem.

in this case, I have created all certificates today. That means they will all expire together and I set the cron to 60 days. Its still 30 days before they will expire.

This should work, right?
 
Hi Marc77,

as I wrote, it IS possible, but not recommended... just imagine, adding new (sub)domains in the future - I can nearly assure you, that you will accidently miss a renew - date. ;)
 
Back
Top