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

Recent content by Sebastian Lange

  1. S

    Resolved Letsencrypt fails to secure domain (and plesk panel)

    Hi, sorry for the long wait. We did not secure it manually it was secured by default plesk ssl self signed certificate. I just wondered why the option in the letsencrypt module would be available but not working. Since its only me working on plesk all of the time this is no big deal. It did work...
  2. S

    Resolved Letsencrypt fails to secure domain (and plesk panel)

    After several reboots and (not so sure what I did) different renewals and server-restarts the homepage is now correctly using the letsencrypt certificate. Plesk panel still has the same issue of not getting the letsencrypt cert. Insists on using the Odin-generated Plesk certificate and does not...
  3. S

    Resolved Letsencrypt fails to secure domain (and plesk panel)

    I tried to update different modules using pip but found out, I am missing the complete headers in Still not able to use letsencrypt
  4. S

    Resolved Letsencrypt fails to secure domain (and plesk panel)

    The letsencrypt module fails to secure the (only) domain and the plesk panel on a fresh installed plesk system with a restored domain from backup (by Odin). There are currently just the default preinstalled plesk-panel default certificate under Tools->SSL Certs and the not working letsencrypt...
See more
Back
Top