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