TorbHo
Regular Pleskian
- Server operating system version
- Ubuntu 24.04 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.81 Update 9
Hello,
we use the "TuxCare Extended Lifecycle Support for PHP" extension on our Plesk servers with older websites. PHP 7.4 was installed via the extension and the affected sites were switched to "7.4.33 (Secured)".
1. TuxCare packages are not updated automatically
The extension and its description gave us the impression that the secured PHP versions are kept up to date automatically. However, today `apt list --upgradable` showed 26 pending updates for alt-php74 (installed 7.4.33-83, candidate 7.4.33-86 from repo.alt.tuxcare.com). Nothing was installed automatically, so we had to update the packages manually via apt.
Our current settings:
- Automatic Plesk updates: enabled
- "Automatically install updates for third-party components shipped by Plesk": enabled
- "Automatically install system package updates" (System Updates tool): enabled
- "Enable safe updates for system packages": enabled
Questions:
a) Is this the expected behaviour? Does the TuxCare PHP extension not install updates for the alt-php packages itself?
b) Is there a recommended way to update only the TuxCare alt-php packages automatically? Could the extension, the "third-party components" option or the Plesk Installer take care of this?
c) Is there a notification (Plesk home page, email) when security updates for the secured PHP versions are available? Since these are EOL versions, we want to make sure we never miss a security fix.
2. Imunify repository is active although Imunify was never installed
While checking where the alt-php updates come from, we noticed that the Imunify repository (repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04) is configured and active on this server. The Imunify extension has never been installed on this server – neither by us nor visibly in Extensions > My Extensions.
This repository also provides alt-php74 packages (7.4.33-44.1 up to 7.4.33-59) with the same APT priority (500) as the TuxCare repository. Currently the TuxCare packages win only because their version number is higher.
Questions:
a) Why is the Imunify repository configured on a server where the Imunify extension was never installed? Which Plesk component or extension adds it (e.g. the TuxCare extension, the Plesk Installer or the automatic Imunify migration from 2025)?
b) Is it safe to remove this repository, or is it required by Plesk or the TuxCare extension? Will it be added again automatically after removal?
c) Why does the Imunify repository contain alt-php74 packages at all, and are they intended to be installed on Plesk servers?
Thank you in advance!
we use the "TuxCare Extended Lifecycle Support for PHP" extension on our Plesk servers with older websites. PHP 7.4 was installed via the extension and the affected sites were switched to "7.4.33 (Secured)".
1. TuxCare packages are not updated automatically
The extension and its description gave us the impression that the secured PHP versions are kept up to date automatically. However, today `apt list --upgradable` showed 26 pending updates for alt-php74 (installed 7.4.33-83, candidate 7.4.33-86 from repo.alt.tuxcare.com). Nothing was installed automatically, so we had to update the packages manually via apt.
Our current settings:
- Automatic Plesk updates: enabled
- "Automatically install updates for third-party components shipped by Plesk": enabled
- "Automatically install system package updates" (System Updates tool): enabled
- "Enable safe updates for system packages": enabled
Questions:
a) Is this the expected behaviour? Does the TuxCare PHP extension not install updates for the alt-php packages itself?
b) Is there a recommended way to update only the TuxCare alt-php packages automatically? Could the extension, the "third-party components" option or the Plesk Installer take care of this?
c) Is there a notification (Plesk home page, email) when security updates for the secured PHP versions are available? Since these are EOL versions, we want to make sure we never miss a security fix.
2. Imunify repository is active although Imunify was never installed
While checking where the alt-php updates come from, we noticed that the Imunify repository (repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04) is configured and active on this server. The Imunify extension has never been installed on this server – neither by us nor visibly in Extensions > My Extensions.
This repository also provides alt-php74 packages (7.4.33-44.1 up to 7.4.33-59) with the same APT priority (500) as the TuxCare repository. Currently the TuxCare packages win only because their version number is higher.
Questions:
a) Why is the Imunify repository configured on a server where the Imunify extension was never installed? Which Plesk component or extension adds it (e.g. the TuxCare extension, the Plesk Installer or the automatic Imunify migration from 2025)?
b) Is it safe to remove this repository, or is it required by Plesk or the TuxCare extension? Will it be added again automatically after removal?
c) Why does the Imunify repository contain alt-php74 packages at all, and are they intended to be installed on Plesk servers?
Thank you in advance!