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

Resolved Deprecation of Let's Encrypt Extension

Martin.B

Plesk Certified Professional
Plesk Certified Professional
According to changelog and some announcements, the support for the Let's Encrypt Extension is going to be droppend and replaced by the SSLIt! Extension.

Does anybody know if the SSLIt!-Extension is going to respect the panel.ini settings, which were set for the Let's Encrypt Extension in the past?
I'm thinking especially about the following settings:

INI:
[ext-letsencrypt]
use-common-challenge-dir = false 
send-notifications-interval = 7 days
allow-wildcard-certificates = false
letsencrypt-url = https://letsencrypt.org/de/
terms-url = https://letsencrypt.org/de/repository/
letsencrypt-docs-rate-limits-url = https://letsencrypt.org/de/docs/rate-limits/

If not, what are the respective options for the new extension?
The most important setting for us is the "allow-wildcard-certificates = false", to disable wildcard certificates, which can only be issued by DNS-validiation.
 
Let's Encrypt will continue to work as a plugin. Some specific options related to Let's Encrypt will continue to work in [ext-letsencrypt] section.
Code:
[ext-letsencrypt]
allow-wildcard-certificates = false
letsencrypt-url = https://letsencrypt.org/de/
terms-url = https://letsencrypt.org/de/repository/
letsencrypt-docs-rate-limits-url = https://letsencrypt.org/de/docs/rate-limits/
will continue to work in LE.
allow-wildcard-certificates totally hide wildcard from the LE and SslIt UI (it disables wildcard support in product)
Code:
send-notifications-interval = 7 days
Also will continue to work, but it is better to specify it in SSLit section.
Code:
use-common-challenge-dir = false
in this case, CCD will not be enabled in SslIt on installation.
 
Back
Top