Question Can TuxCare ELS install older PHP versions on a new Plesk server?

[TorbHo]

Server operating system version

Debian 10

Plesk version and microupdate number

older version

Question:
Can I use TuxCare Extended Lifecycle Support for PHP to install older PHP versions (e.g., PHP 5.6 or 7.0) on a freshly installed server running the latest Plesk version — even if these PHP versions are no longer offered by the OS or by Plesk itself?

Background:
I understand that TuxCare ELS provides security updates for end-of-life PHP versions. What I’m unsure about is whether the older PHP version must already exist on the server so TuxCare can patch it, or whether TuxCare also supplies the full PHP package so that it can be installed from scratch on a modern Plesk setup.

Example scenario:

• I have an older server running an outdated Plesk version where PHP 7.2 is actively used by several websites.
• I plan to migrate everything to a new server with a current OS and a recent version of Plesk, which officially only supports PHP 7.4+.
• Question: Before starting the migration, can I install PHP 7.2 on the new server (e.g., via TuxCare ELS) so that all sites continue to work during and after the migration?
  Or does TuxCare require an already installed PHP 7.2 base package that it only patches, rather than providing the complete legacy PHP interpreter?

 

[Sebahat.hadzhi]

Hi, @TorbHo . You should be able to install and configure PHP versions (5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0) through the extension itself:

plesk ext tuxcare-php --install-configure -version 7.2

I will test that tomorrow to be sure and update you with confirmation.

 

[Sebahat.hadzhi]

Hi again, @TorbHo . So, what I said previously is not entirely correct - apologies for misleading you. The PHP version has to be already present on the server and must be packaged by Plesk, i.e. not by the OS vendor. Then, the aforementioned command will install and configure the corresponding TuxCare ELS PHP version in the same way that Plesk PHP is configured.

 

[TorbHo]

Thanks for the clarification. However, I don’t quite understand the benefit of the extension – if Plesk still has to provide the PHP version itself, that means Plesk would still need to be an old version. Doesn’t that basically defeat the purpose of keeping older PHP versions up to date while using an up to date OS through TuxCare?

 

[Sebahat.hadzhi]

My understanding is that he PHP version packaged by Plesk is used as the base packaging structure, which is why it is needed. TuxCare provides the actual security-patched PHP builds through the extension. The extension installs these TuxCare-maintained PHP packages into the Plesk PHP environment, so you manage them the same way as native Plesk PHP versions. I will inquire with one of our developers if further details are needed, please let me know.

 

[TorbHo]

Thanks for the explanation. One more question: does it have to be the official PHP version provided by Plesk, or could I also install PHP 7.2 from an alternative source and add it to Plesk, and then use it with the extension afterward?

 

[Sebahat.hadzhi]

Thank you for the update. No, if it is shipped by an alternative source, the extension will not detect it. What OS are we talking about please - Debian 12?

 

[ChristophRo]

Thanks for the clarification. However, I don’t quite understand the benefit of the extension – if Plesk still has to provide the PHP version itself, that means Plesk would still need to be an old version. Doesn’t that basically defeat the purpose of keeping older PHP versions up to date while using an up to date OS through TuxCare?

Seems like somewhat of a clusterf*ck in my opinion and also not what I expected it to be (from reading the release notes)
Also leads to the somewhat silly situation, that on Debian 13 I can get PHP 7.0 trough 8.5, while on Debian 12 it's only possible to get 7.4 to 8.5...

But on Debian/Ubuntu you're better off using the alternative/older PHP versions from deb.sury.org anyway

We do not use/install any of the Plesk PHP versions anymore (except for the one that Roundcube requires - but we then disable that one afterwards) and only use the alternative ones.
As least they get also patched (backported from more recent versions that still get support from the PHP foundation), wherever Plesk does not do that, but still allows you to use/install them on your server.
i.e. any as "outdated" marked PHP version that is provided by Plesk, is potentially insecure.