We’ve released Let’s Encrypt Extension 2.4.0:

https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt

Changelog (see also https://docs.plesk.com/release-notes/onyx/change-log/#1753-mu20171017 ):
2.4.0 (16 October 2017)
[+] The customers are now notified by email about automatic certificate renewal, both successful and failed. This behaviour can be configured in Tools & Settings – Notifications.
[*] In error reports, technical details are now grouped together in a collapsed text block.
[*] The certificate used for securing mail service will now be renewed and applied automatically. Several issues with renewing certificates were fixed.
[*] On Windows servers, domain certificates used for securing Plesk Panel are now actually renewed instead of removing old certificate and issuing a new one. (Only for Plesk 17.8 and later.)
[-] When creating a subscription or domain with an internationalized domain name, automatic installation of a Let's Encrypt certificate failed. (EXTLETSENC-329)
[-] If Let's Encrypt Authority rejects the request with "Policy forbids issuing for name", the error message now provides relevant information and a reference link. (EXTLETSENC-202)
[-] The certificate used for securing Plesk Panel was not shown in the certificate repository. (EXTLETSENC-187)
[-] Under certain circumstances, the certificate for Plesk Panel was not renewed upon updating the Let's Encrypt extension from versions earlier than 2.0. (EXTLETSENC-322)
[-] When issuing a certificate for a webmail addon domain, if an error occurred, the error message did not provide a relevant explanation. (EXTLETSENC-321)
[-] On Windows servers, symbolic links to certificates were created with extra \ symbols, which prevented opening them with some applications, for example with notepad.exe. (EXTLETSENC-315)
Shared publiclyView activity