• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Will LetsEncrypt auto-renew?

Peter99

Basic Pleskian
As i said, we're used to Plesk/Lets-Encrypt doing auto-renewals every month.
It missed last month however i can from our websites on the server.
We have got 2 different CentOS servers and the "issue?" is the same on both servers.

Certificate screenshot from browser:
Gyazo - c876ffc8c0dad060aff7606c537122b4.png

I have attempted to run the renewal script manually from the SSH terminal, and i get this:

[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
[2017-05-01 13:44:38] DEBUG [extension/letsencrypt] Skip renew *domain goes here*: too early for expiration date 2017-06-23
...... and so on.

Does anyone know if the auto renewals no longer update the certificate until the very last month of the certificate being valid, instead of every month?
Or should i worry that i have to manually update all certificates from customers (aprox. 500 certs) on Plesk > Lets Encrypt > Subscription > Renew button ?
 
Closing my question.
I saw this changelog post:
  • Granular and reliable renew process: the extension now performs a daily check for certificates which are about to expire and renews them not earlier than 30 days before their expiration
 
Back
Top