Skip to content

Available Software Versions - Ubuntu 20.04 (Focal)

If you plan to upgrade operating system to Ubuntu 20.04, either of your own accord, or because you were advised to do so by one of our employees, you need you decide which versions of software are you going to use. This article contains a list of software versions available in Debian Buster.


The only available version is 2.4. Other versions cannot be installed. Details about incompatible changes are available on the Apache web server website. One of the most common sources of problems is the new access management module. That can be solved by installing mod_access_compat. 


  • 7.x

By default, we install the latest version available in developer’s official repository. There are no incompatible changes between minor versions.


  • 2.0

HAProxy’s configuration is usually compatible even between major versions. In some cases, slight changes are necessary. However, those are done by our administrators as part of the upgrade process. Only in case you provide your custom configuration, you need to update it yourself.


  • OpenJDK 8
  • OpenJDK 11
  • OpenJDK 14
  • OracleJDK - license required!


  • 3.x
  • 4.x

ManticoreSearch is database for full-text search. It is the successor to SphinxSearch, version SphinxSearch 2 is compatible with ManticoreSearch version 2. When migrating to ManticoreSearch version 3, the index_converter configuration migrator can be used.


  • 4.4

Versions 4.x are stable and do not cause problems in production, but you need to check the compatibility with your applications. In-place upgrade from version 3.6 is possible.

MySQL / MariaDb

  • MariaDB 10.3
  • MariaDB 10.4
  • MariaDB 10.5

MariaDB is a fully compatible substitute for MySQL. We recommend version 10.3, but there are numerous incompatibities with the widely used 10.1 version, resp. MySQL 5.6. You should thoroughly test your application on the version before upgrading. Some incompatible changes can be tweaked using SQL_MODE


  • 1.18

We install stable versions only. The mainline versions (odd numbers) are not suitable for use in production environments in our experience. 


  • 10
  • 12
  • 14


  • 2.4

This version is compatible even with older clients.


  • 11 - recommended
  • 12
  • 13

Upgrades usually go without complications. There are few incompatible changes between versions. If you are using an older version, please check the support policy on the project’s website.


  • 5.6 -the oldest version available for install (not as Apache module on Plesk servers)
  • 7.3
  • 7.4 - recommended, if compatible with your application
  • 8

You can find the details about versions’ life cycles on the PHP website. To ensure the security of your applications, use only supported versions! 


  • 3.8


  • 5.0

Redis 4 and higher in cluster mode are incompatible with older clients and applications. If your application requires an older version, you need to stay at Debian Stretch.


  • 2.2


  • 6.2

Varnish configuration is always provided by the customer, because it must be tailored to their application. If the configuration format has changed between versions, you need to send an updated configuration before the upgrade. We install Varnish only in cases, where the application’s performance is unacceptable without it.