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

Forwarded to devs Lets Encrypt Link gives Error Message, Won't Load

G J Piper

Regular Pleskian
TITLE:
Lets Encrypt Link gives Error Message, Won't Load
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Product version: Plesk Onyx 17.5.3 Update #13
Update date: 2017/07/11 12:13
Build date: 2017/03/17 16:00
OS version: CentOS 6.9
Revision: 55d1b49a272f44666e1920eca8b6e4da449a38cd
Architecture: 64-bit
Wrapper version: 1.2
PHP 7.1.7
PROBLEM DESCRIPTION:
When clicking the link:
Domains -> <domain.ext> -> Let's Encrypt
I get the error message, attached:

lets-encrypt-error-20170711.jpg
STEPS TO REPRODUCE:
Follow steps in problem description.​
ACTUAL RESULT:
Cannot access individual domains' Let's Encrypt Preferences (for adding to webmail or "www", etc)​
EXPECTED RESULT:
Setting opens up as normal.​
ANY ADDITIONAL INFORMATION:
I did update the Let's Encrypt extension to version 2.2.0-128 earlier today.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Have you tried to re-install LE extension?
Would like to avoid that if possible since it is protecting dozens of customer domains currently. Does re-installing take only a minute, globally? Or will I have to re-enable it on all the domains individually again? How would you do it?
 
Hello!

Thank you for the bug report. We confirm an issue EXTLETSENC-221 on our side: an issue occurs while processing another error, which take place on your domain. So, instead of clear error message (or automatic resolving) you got a white screen with noted internal error. We will fix it as soon as we can, I apologise for the incenvinience.

That's about the root cause, could you please check is mail service enabled on your domain? It not, could you please enable it and try to sign domain again? It could be a workaround.
 
Last edited:
Hello!

I glad to introduce Let's Encrypt 2.2.1 (Let's Encrypt - Plesk Extensions), where the issue EXTLETSENC-221 fixed. And, again, thank you for feedback!

I updated to your new version of the extension and it is indeed fixed! Thank you!

This server's domains all have mail turned off, because mail is handled on a completely different server. (which brings other issues with Let's Encrypt on the mail server, but those aren't bugs -- rather shortcomings in the design of the cert verification system)
 
Back
Top