Question Upgrade Almalinux 8 to 9 with Plesk installed

[G J Piper]

I'm just wondering why they didn't just go with an Alma8to10 script so we could actually get ahead of this game and stay there.

 

[Azurel]

I don't think a script for “8to10” makes much sense. A “9to10” script would be better. You'd just have to run both (8➜9, 9➜10), that way everyone using AlmaLinux 9 could benefit from it right away. I'm also hoping for a script like that, since I'd like to switch to AlmaLinux 10 as well (from AlmaLinux 8).

There’s already a basic script for this from AlmaLinux “9to10” since July 2025: ELevate to EL 10!

 

[G J Piper]

A “9to10” script would be better.

I agree completely now that I'm on AlmaLinux 9. ;-)

 

[Azurel]

Requirements for converting are:

PHP-7.1, 7.2, and 7.3 is not supported (for now), so conversion will be refused once one of them is installed

My server was originally upgraded from CentOS 7 to AlmaLinux 8, which is why my "PHP by OS vendor" is still stuck on version 7.2 (it's not used). Since this is the OS vendor PHP, I cannot remove or change it via the Plesk Components Installer. What is the officially recommended and safest way? Should it be removed or switch to PHP 7.4?

 

[Sebahat.hadzhi]

@Azurel , I just consulted with our devs who created the script and they confirmed that if it's OS vendor PHP, you can remove it through package manager (dnf, yum) but you have to make sure your domains are not run by OS vendor PHP-7. Since it's OS PHP, there is nothing Plesk can provide, AlmaLinux-9 has PHP-8 so you already have to switch to PHP-8.x (preferably Plesk variants).

 

[IgorG]

Tried to apply announced AlmaLinux 8 to 9 upgrade script. And stuck at the following error:

2026-07-25 12:51:54,275 - ERROR - almalinux8to9 process has failed. Error: Failed: doing the conversion. The reason: Leapp preupgrade failed due to preventing factors bei
ng found.
Original exception: Command '['/usr/bin/leapp', 'preupgrade']' returned non-zero exit status 1..
The preventing factors are:
Detected RPMs with RSA/SHA1 signature:
Digital signatures using SHA-1 hash algorithm are no longer considered secure and are not allowed to be used on RHEL 9 systems by default. This causes issues when using D
NF/RPM to handle packages with RSA/SHA1 signatures as the signature cannot be checked with the default cryptographic policy. Any such packages cannot be installed, remove
d, or replaced unless the signature check is disabled in dnf/rpm or SHA-1 is enabled using non-default crypto-policies. For more information see the following documents:
  - Major changes in RHEL 9: https://red.ht/rhel-9-overview-major-changes
  - Security Considerations in adopting RHEL 9: https://red.ht/rhel-9-security-considerations
 The list of problematic packages:
    - plesk-libboost-chrono1.74 (DSA/SHA1, Thu 02 Dec 2021 02:59:14 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-filesystem1.82 (DSA/SHA1, Tue 23 May 2023 04:44:54 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libmariadbclient-3.0 (DSA/SHA1, Thu 30 Apr 2020 07:21:45 PM +07, Key ID bd11a6aa914bdf7e)
    - pp18.0.61-bootstrapper (DSA/SHA1, Mon 03 Jun 2024 02:54:34 PM +07, Key ID bd11a6aa914bdf7e)
    - pp18.0.59-bootstrapper (DSA/SHA1, Thu 29 Feb 2024 05:15:44 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-liblog4cpp-0.3.5 (DSA/SHA1, Thu 01 Mar 2018 08:04:13 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-regex1.74 (DSA/SHA1, Thu 02 Dec 2021 02:59:14 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-serialization1.79 (DSA/SHA1, Fri 03 Jun 2022 10:53:23 AM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-chrono1.79 (DSA/SHA1, Fri 03 Jun 2022 10:53:25 AM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-locale1.79 (DSA/SHA1, Fri 03 Jun 2022 10:53:25 AM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-date-time1.65 (DSA/SHA1, Thu 01 Mar 2018 08:04:11 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-nodejs12 (DSA/SHA1, Mon 28 Oct 2019 01:35:22 PM +07, Key ID bd11a6aa914bdf7e)
    - oniguruma5php (DSA/SHA1, Tue 17 Oct 2023 09:34:17 PM +07, Key ID 004e6f4700f97f56)
    - plesk-libboost-chrono1.82 (DSA/SHA1, Tue 23 May 2023 04:44:55 PM +07, Key ID bd11a6aa914bdf7e)
    - sw-engine-cli-5.59 (DSA/SHA1, Tue 30 Jan 2024 09:10:05 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libstdc++13.2.0 (DSA/SHA1, Tue 12 Mar 2024 02:50:35 AM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-serialization1.80 (DSA/SHA1, Mon 05 Sep 2022 05:55:39 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-1.82 (DSA/SHA1, Tue 23 May 2023 04:44:53 PM +07, Key ID bd11a6aa914bdf7e)
    - atomic-curl-libcurl (RSA/SHA1, Mon 22 Feb 2016 09:43:35 PM +06, Key ID ffbd5d0a4520afa9)
    - plesk-libboost-1.74 (DSA/SHA1, Thu 02 Dec 2021 02:59:12 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-regex1.80 (DSA/SHA1, Mon 05 Sep 2022 05:55:39 PM +07, Key ID bd11a6aa914bdf7e)
    - plesk-libboost-1.80 (DSA/SHA1, Mon 05 Sep 2022 05:55:41 PM +07, Key ID bd11a6aa914bdf7e)
    - sw-engine-cli-6.66 (DSA/SHA1, Tue 26 Nov 2024 02:53:27 PM +07, Key ID bd11a6aa914bdf7e)

Any solutions?

 

[IgorG]

Any solutions?

Nevermind. Removed with --nodeps all these orphaned packages and successfully dist-upgraded in almost 5 hours.