• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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