Facebook
TwitterAs 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 ?
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 ?
