• 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 LetsEncrypt extension is suddenly reliant on DNS feature which is not enabled on my servers

mr-wolf

Silver Pleskian
Plesk Guru
TITLE:
LetsEncrypt extension is suddenly reliant on DNS feature which is not enabled on my servers
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.8 / Ubuntu 16.04.4 LTS
PROBLEM DESCRIPTION:
I have enabled wildcard certificates per this tutorial by editing
/opt/psa/admin/conf/panel.ini

Getting Free Wildcard SSL/TLS Certificates from Let's Encrypt

I have DNS centralized on 1 Plesk server which is not running any websites.
The Plesk servers running websites do NOT have the DNS extension enabled

When I click "renew certificate" I get this error:
View attachment 14575
STEPS TO REPRODUCE:
On a server without DNS renew LetsEncrypt certificate​
ACTUAL RESULT:
Get error
upload_2018-7-11_9-35-48.png
EXPECTED RESULT:
Just renew LetsEncrypt certificate like it always did​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 

Attachments

  • upload_2018-7-11_9-33-21.png
    upload_2018-7-11_9-33-21.png
    19.2 KB · Views: 9
Thank you.
Bug EXTLETSENC-558 is confirmed. It will be fixed in the nearest update of Let's Encrypt extension.
 
Back
Top