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

    Resolved Let's encrypt: Connection unsecure

    Yes, I had. The problem still wasn't solved. But I found a solution: Restarting the server. Maybe the Let's Encrypt module hung up somewhere, without throwing out errors. It took me so much time, although the solution was that easy. Thanks for your time to help me.
  2. C

    Resolved Let's encrypt: Connection unsecure

    Hi Peter, currently, I am not using webmail on any domain, so the checkbox for webmail is disabled. The box for the aliases (www.) is checked. If I click on Renew, it's still the same problem. The date is still 16.02.2019
  3. C

    Resolved Let's encrypt: Connection unsecure

    Hello, I've bought 3 months ago Plesk Web Pro Edition. Now, 3 months are passed, I have problems with the Let's Encrypt certificates. I bought several new domains a few days ago (2-14 days) and added them to my panel. But every time I secure them with Let's Encrypt, I just got this error when...
Back
Top