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

Plesk Panel Upgrading...

NeuroPsyche

Regular Pleskian
It has become apparent that during upgrades of Plesk that certain files and databases become corrupt.
This has happened in almost every significant release that I've upgraded from.

I'd like to pose a question to all...
During the upgrade procedures using the Auto-Installer/Upgrade, does it lock/protect files that may be open?
For example: Customers online modifying their sites, users online view sites, databases open/active?

So.. with this question posed, could the corruption of files/databases be happening because the auto-upgrade program does not lock/protect files from the upgrade process and should possibly services be stopped during upgrades to prevent issues?

Thanks!

David
 
Back
Top