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

Question Dist-upgrade path for Debian 10 server already on Plesk Obsidian 18.0.82

TexcoSL

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
18.0.82.3
Hello,

We have a Plesk server on Debian 10 (buster) that has already been updated to Plesk Obsidian 18.0.82.3. Our goal is to reach Debian 13 (trixie), the recommended OS, keeping the server in place (no migration).

The documented path is Debian 10 > 11 (manual procedure in KB 12377714344983), then debian11to12 and debian12to13. However, Plesk 18.0.81 is the last release supporting Debian 11, and when we run:

plesk installer --override-os-version 11 --show-releases

the installer returns: "ERROR: There are no suitable product versions."

So the manual Debian 10 > 11 procedure (steps "plesk installer --override-os-version 11 --check-updates" and "plesk installer update" on Debian 11) seems impossible once 18.0.82 is installed.

Questions:
1. Is there a supported in-place path from Debian 10 to Debian 12 or 13 for a server already on Plesk 18.0.82 (for example, a Debian 10 > 12 procedure, a temporary Debian 11 build of 18.0.82, or a supported downgrade to 18.0.81 before the dist-upgrade)?
2. If not, is Plesk Migrator to a new Debian 13 server the only supported option?
3. For servers still on Plesk 18.0.81 and Debian 10: is the path 10 > 11 (manual) > 12 (debian11to12) > 13 (debian12to13) supported, and must they stay on 18.0.81 until they reach Debian 12?

Server details: KVM virtual machine (OVHcloud VPS), MariaDB 10.3.39, PHP handlers from Plesk (7.4, 8.0, 8.1, 8.2, 8.3), Imunify360 and the Monitoring extension installed.

Thank you.
 
Hi, @TexcoSL . I consulted with our team about your case. Although the OS upgrade and the Plesk upgrade are separate processes and an in-place upgrade is technically possible this is not an officially documented procedure and carries more risk than a standard dist-upgrade. Debian does not support skipping releases, so you can't go straight from Debian 10 to 12 or 13. The path is 10 > 11 > 12 > 13. So, a migration would be the preferred method in your case. Regardless of which path you decide to take, please make sure to have a full VM snapshot.
 
@TexcoSL

That's a very interesting case. Plesk’s Extended Lifecycle Support (ELS) program is available for Debian 10, but not for Debian 11. As a result, many customers running Debian 10 with this paid support are now unable to perform in-place distribution upgrades after upgrading Plesk from 18.0.81 to 18.0.82.

So, basically, you paid extra for this support, and now you’re facing a much bigger bill. In effect, ELS has made things worse. Since you’re a paying customer, I would open a support ticket with Plesk, report this “bug,” and ask them to help with the upgrade to Debian 12. Because their Support is exactly for this case: you are on a supported OS and you cannot upgrade your server to the next supported OS. And the Plesk migrator cannot be an excuse for this situaton.
 
Back
Top