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

    Resolved 500 Plesk\Lock\Exception

    Seems to be fixed/working again after upgrading via console to 18.0.41
  2. U

    Issue Connection refused for update / upgrade site

    Same here. I also made a reboot yesterday for some other reasons. But the upgrade via web is not yet possible anymore.
  3. U

    Issue Connection refused for update / upgrade site

    Same issue on my servers since the fixed upgrade version for old kernels.
  4. U

    Resolved 500 Plesk\Lock\Exception

    Same issue here after upgrade to 18.0.40-mu1. Any ideas?
  5. U

    Resolved 500 Plesk\Lock\Exception

    By using the (incrementel) backup function which Server4You provides. In addition I have some scripts running to backup some important stuff on a daily basis. With this I was able to bring the server back to the state before the plesk upgrade. For now, the Plesk updates are disabled until the...
  6. U

    Resolved 500 Plesk\Lock\Exception

    I have the same issue using a vserver from Server4You. Meanwhile I recovered the state before upgrading Plesk to 18.0.40 until the fixed version is available.
Back
Top