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

Plesk 12.5.30 - Update Question

Marco_R

New Pleskian
Hello, i run Plesk 12.0.18 - Update #70 on a CentOS 6.6 machine. What about automated upgrade by panel ? .. can anyone tell me if he found major problems in the control panel after rebooting ?. Thanks : Regards.
 
After an upgrade to 12.5.30 you may experience issues with PHP, because the Apache worker module may change and leave the PHP5 module de-activated. If you set it to worker MPM and activate the PHP5 module again, things will be as they used to be.

You will also likely run into issues with Fail2Ban. If this prevents an update, fully remove all fail2ban modules first (via SSH, use not only "yum remove fail2ban", but "yum remove fail2ban\*", else some fail2ban libraries will remain on the system), then do the upgrade, afterwards re-install fail2ban using "yum install fail2ban".
 
Back
Top