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

Search results

  1. R

    Vote Let's Encrypt support

    Thanks IgorG. I hadn't upgraded to 12.5 yet, so it wasn't showing. I've used it now and it works great. How can we use the Let's Encrypt certs to secure the panel? The certificates aren't appearing in "/admin/ssl-certificate/list"
  2. R

    Vote Let's Encrypt support

    FWIW, the answer to my question was to just upload the release and run "./letsencrypt-auto" from the shell. With the public beta underway I have successfully configured some domains, and plan to slowly roll it out to a few more over the next week.
  3. R

    Vote Let's Encrypt support

    Thanks UFHH01 - With your quote above, the link to the releases actually has four releases listed. That is why I assumed it was good to go.
  4. R

    Vote Let's Encrypt support

    IgorG - Feeling like a noob here, but how do we install it? The readme is a bit sparse. When I try to add it through the Extensions panel, I get "Error: Unable to install the extension: Corrupted meta.xml file." I cant see meta.xml anywhere in the project. Do we need to run the scripts manually?
Back
Top