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

Issue LetsEncrypt extension can not handle a webmail certificate for mail-only domains

mr-wolf

Silver Pleskian
Plesk Guru
I have several "mail only" domains on my Plesk server and it's not possible to enable the LetsEncrypt certificate for those.
As a workaround I could create a dummy site for those domains, but I would prefer not to do this as this could lead to misunderstandings. I prefer to have only a website configured if it is actually running on that Plesk.

[EDIT]
Such a workaround would only work if the site is really referring to that specific server. Sometimes it's handled by another server, sometimes even not even one that I manage.

The LetsEncrypt procedure would fail as the main site does not resolve. I haven't tested if this means that the "webmail.<domain>" survives. I don't think it does, but even if it does it would still be a messy procedure.
 
Last edited:
Back
Top