• 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.

Update of the LetsEncrypt component always fails since its introduction

mr-wolf

Silver Pleskian
Plesk Guru
TITLE:
Update of LetsEncrypt always fails since its introduction
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.5.3, Ubuntu 16.04 LTS, Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz
PROBLEM DESCRIPTION:
Whenever a new LetsEncrypt extension is released I will be notified of it, but the upgrade always fails.
This happens/happened on 6 different servers (of which now only 3 remain) on at least 3 occasions.

It does not happen with upgrades of other components​
STEPS TO REPRODUCE:
When upgrade is offered I go ahead and install.
It then fails, I believe it's a 'cp' command.

After trying it several times I give up and remove the component letsencrypt and install it again afterwards.
This never failed thus far.

The latter is also the reason why I never reported this before as I am constantly very busy. I can only assume this is also the reason why many others didn't give feedback on this.

I have seen forum entries of others experiencing the same.​
ACTUAL RESULT:
Update procedure can't be completed.

Workaround of removing component and installing it again does.​
EXPECTED RESULT:
Update LetsEncrypt completes the procedure.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
BTW.... The Plesk Team has access to my server at the moment and are looking into other issues... They could easily grab some log if they need to.
If I can provide you of some log, please tell me which one.
 
Back
Top