Plesk Lifecycle Policy
Plesk continues to evolve from a basic and feature-based control panel to a powerful management platform proven on Server, Sites, Apps, Hosting & Cloud Businesses. Rapidly changing technologies require an update to the Plesk Lifecycle and End-of-Life (EOL) policy. This new approach supports Plesk users in staying ahead of the game and mitigating security risks, by making it easier for Plesk partners and customers to always be on the latest software version.
- No need to upgrade or migrate to a new major version each year
- Immediate access to new features or improved existing ones
- Constantly patching potential security vulnerabilities
- Boosted speed and performance
- Protection of user’s data
With the launch of Obsidian, Plesk is ending the era of upgrades and introducing a monthly release cycle. Switching to monthly updates is imperative to always delivering a secure and stable version of Plesk with new features and improvements that Partners and Customers expect to get from an intelligent software solution.
In the past, Plesk used to launch one major version per year and users were required to upgrade the Plesk server (e.g. 12.x > 17.x). With Plesk Obsidian, users are strongly recommended to allow automatic updates through Plesk Server settings so they will automatically be on the latest version including hotfixes, security patches, micro updates, and more. This dedicated blog article offers additional details about monthly updates and the changed approach.
- An up-to-date and supported Plesk installation with all the latest available updates installed is a prerequisite for technical support from Plesk.
- Security patches, security updates and/or hotfixes are NOT shipped when automatic updates are disabled.
Plesk highly recommends to enable automatic updates if the user wants the Plesk server(s) to be stable and secure and have access to support.
Plesk Lifecycle Policy
- A major version is defined as a change of the first digit(s) of any Plesk version number. For example, Plesk Onyx (17.x) and Plesk Obsidian (18.x) are different major versions. Starting with Plesk Obsidian, version 18 will remain a major version that will be supported.
- For Plesk Obsidian (18.x), software patches are provided and support requests are accepted for the latest available update of this major version as well as the preceding update (see example). For all other versions, the Plesk version life cycle table below applies.
Plesk Version LifecycleThe table below describes when specific versions of Plesk will enter the Extended Support phase and when patches / support will no longer be available. If the Plesk version in use is EOL (End Of Life), Plesk strongly recommends to upgrade to a supported Plesk version:
END OF LIFE**
June 4, 2019 ***
October 11, 2016
October 11, 2020
April 20, 2021
June 16, 2014
June 16, 2018
January 1, 2019
June 13, 2012
June 13, 2016
December 13, 2016
November 3, 2010
January 31, 2015
May 3, 2015
December 9, 2008
December 9, 2012
June 9, 2013
September 20, 2006
March 1, 2012
Small Business Panel ****
August 1, 2011
Plesk 7 and earlier
February 10, 2004
January 1, 2012
*In terms of Plesk Onyx, Extended Support is a 4-year period, after which the product will no longer be available for new purchases and will only receive patches for critical issues. The Extended Support Period is six (6) months.
**End-of-Life: Once the Extended Support period is over, the product will stop receiving further development (including critical patches), and technical support requests will no longer be accepted.
*** Starting from this date, Plesk began accepting technical support requests for Plesk Obsidian (General Availability version launched on October 22nd, 2019).
**** The upgrade path for Small Business Panel customers involves a migration to Plesk 10, where these products were merged.
Currently Supported OSes
The table below lists all operating systems which are receiving updates and support from the OS vendor and are therefore supported by a current and supported version of Plesk. Visit the Software Requirements section of the Plesk release notes for more information about OS compatibility of a particular Plesk release.
*Plesk recommends using the latest supported version of an operating system when deploying a new server because a server with a current OS has the longest potential lifetime before its OS Vendor Termination Date.
*Important: Due to the early End-of-Life of CentOS 8, Plesk highly recommends using AlmaLinux OS or RockyLinux as alternatives going forward. Both are supported by Plesk Obsidian 18.0.41, available from January 18th, 2022.
VENDOR TERMINATION DATE
Ubuntu 22.04 Server LTS
Ubuntu 20.04 Server LTS
RedHat Enterprise Linux 8
May 2029 (end of production phase)
RedHat Enterprise Linux 9
Rocky Linux 8
Windows Server 2016
January 11, 2027
Windows Server 2019
September 1, 2029
Windows Server 2022
CloudLinux OS Shared 8
May 31, 2029
May 31, 2023
Windows Server 2012 R2
Windows Server 2012
Virtuozzo Linux 7
June 30, 2023
RedHat Enterprise Linux 7
June 30, 2024 (end of production phase)
June 30, 2024
June 30, 2024
Plesk does not accept support requests and will not issue software patches for servers with OSes that are not listed in the table above, or if their Vendor Termination Date is past due.
Plesk does not accept technical support requests for preview versions of Plesk. Bug reports and technical questions for preview versions should be submitted through the Plesk Community Forum. Feature requests should be submitted through the Plesk User Voice.
For older unsupported versions of Plesk servers, Plesk strives to assist and accept technical support requests, but only the ones related to upgrading to a supported version or environment. Exceptions are updates from and to preview versions, since the stability of such upgrades is not guaranteed.
If a user’s Plesk version is approaching its End of Life phase or the OS is approaching its Vendor Termination Date, Plesk recommends migrating to the latest Plesk version and a supported operating system. If a user needs migration instructions, advice, or if the user would prefer to let Plesk professionals handle the migration, the user should contact the Plesk Professional Services team.