Facebook
Twitter- Server operating system version
- Multiple
- Plesk version and microupdate number
- Multiple
Title: Request for Comprehensive TuxCare Coverage Matrix — Operating Systems and PHP Versions
I'd like to suggest that Plesk publish a comprehensive, regularly updated reference explaining exactly what TuxCare covers within the Plesk environment, particularly as it relates to operating system and PHP extended security support.
While there is information scattered throughout the Plesk website and knowledge base, I've found it difficult to locate a single, definitive source that clearly explains which operating systems and PHP versions require TuxCare, which are already covered by standard Plesk support, and which combinations may require additional licensing.
Ideally, this would include two separate coverage matrices:
1. Operating System Coverage
For each operating system and version supported by Plesk, including AlmaLinux, Rocky Linux, Ubuntu, Debian, and any legacy operating systems eligible for extended support:
A similar matrix showing:
Perhaps most importantly, a combined matrix showing real-world configurations.
For example:
Another important distinction is understanding the difference between an outdated software version and one that is receiving backported security fixes.
For example, a PHP installation may continue to report an older version number even though security vulnerabilities have been patched. It would be useful to explain how administrators can verify the actual security patch level and distinguish between unsupported software and software receiving extended security maintenance.
Why This Would Be Helpful
As a hosting provider managing multiple Plesk servers with different operating systems and PHP versions, we need to make informed decisions about security, licensing, upgrades, and customer recommendations.
We also need to explain to customers why an older PHP version may still receive security fixes, what those fixes actually cover, and when an upgrade becomes necessary.
Currently, piecing this information together from multiple documentation pages makes it unnecessarily difficult to determine exactly what protection is available for a particular server configuration.
A single, regularly maintained Plesk/TuxCare compatibility and coverage matrix would be an extremely valuable resource for administrators and hosting providers.
Is such a document already available? If not, would Plesk consider publishing one that consolidates this information and keeps it current as operating systems and PHP versions reach their respective end-of-life dates?
I'd like to suggest that Plesk publish a comprehensive, regularly updated reference explaining exactly what TuxCare covers within the Plesk environment, particularly as it relates to operating system and PHP extended security support.
While there is information scattered throughout the Plesk website and knowledge base, I've found it difficult to locate a single, definitive source that clearly explains which operating systems and PHP versions require TuxCare, which are already covered by standard Plesk support, and which combinations may require additional licensing.
Ideally, this would include two separate coverage matrices:
1. Operating System Coverage
For each operating system and version supported by Plesk, including AlmaLinux, Rocky Linux, Ubuntu, Debian, and any legacy operating systems eligible for extended support:
- Whether the operating system is currently supported by its original vendor.
- Whether Plesk officially supports that operating system.
- Whether TuxCare is required, optional, included, or unavailable.
- Exactly which operating system components and security vulnerabilities TuxCare patches.
- Whether TuxCare coverage requires an additional license or is included with a particular Plesk license.
- What happens when the operating system reaches its standard end-of-life date.
A similar matrix showing:
- Which PHP versions receive security updates directly through Plesk.
- Which PHP versions require TuxCare for continued security patching.
- Whether TuxCare PHP coverage is included with certain Plesk licenses or requires an additional purchase.
- Which PHP handlers and installation methods are eligible.
- Whether coverage differs depending on the underlying operating system.
- The expected end-of-support dates for each PHP version.
Perhaps most importantly, a combined matrix showing real-world configurations.
For example:
- AlmaLinux 8.10 with PHP 7.4, 8.1, 8.2, 8.3, or 8.4.
- AlmaLinux 9 with those same PHP versions.
- Ubuntu 22.04 and 24.04 with those same PHP versions.
- Other supported operating systems and PHP combinations.
- No additional TuxCare coverage.
- TuxCare for PHP only.
- TuxCare for the operating system only.
- TuxCare for both the operating system and PHP.
Another important distinction is understanding the difference between an outdated software version and one that is receiving backported security fixes.
For example, a PHP installation may continue to report an older version number even though security vulnerabilities have been patched. It would be useful to explain how administrators can verify the actual security patch level and distinguish between unsupported software and software receiving extended security maintenance.
Why This Would Be Helpful
As a hosting provider managing multiple Plesk servers with different operating systems and PHP versions, we need to make informed decisions about security, licensing, upgrades, and customer recommendations.
We also need to explain to customers why an older PHP version may still receive security fixes, what those fixes actually cover, and when an upgrade becomes necessary.
Currently, piecing this information together from multiple documentation pages makes it unnecessarily difficult to determine exactly what protection is available for a particular server configuration.
A single, regularly maintained Plesk/TuxCare compatibility and coverage matrix would be an extremely valuable resource for administrators and hosting providers.
Is such a document already available? If not, would Plesk consider publishing one that consolidates this information and keeps it current as operating systems and PHP versions reach their respective end-of-life dates?
