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

Resolved General precautions and known caveats for updating 12.5.3 to 17?

Bitpalast

Plesk addicted!
Plesk Guru
We are seeking a list of precautions and known bugs/caveats to plan the update from 12.5.30 to Onyx. For example is it recommended to de-activate ModSecurity and Fail2Ban before trying the upgrade? Are there any known risks, e.g. services that might not start after the upgrade because of changed configuration file locations or other reasons? How do we have to understand that update? Does it replace system libraries or does it only replace Plesk-owned scripts?
 
Back
Top