• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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