Ubuntu 20.04 EOL: what to do with your servers after 31 May?

Five-year standard support for Ubuntu 20.04 LTS (“Focal Fossa”) ends on 31 May 2025 – so Ubuntu 20.04 EOL is barely two and a half months away. After that, Canonical only releases security fixes under Expanded Security Maintenance (ESM), available with an Ubuntu Pro subscription. If you still have 20.04 servers, now is the time to decide what to do with them: an upgrade, a new server, or Ubuntu Pro.

What ends on 31 May?

LTS releases get free security fixes for five years for the packages in the main repository. After that:

  • packages in main only get fixes with Ubuntu Pro, through the ESM-infra service, until 2030,
  • for packages in the universe repository (which includes a lot of popular software), ESM-apps provides fixes, also with Pro,
  • Canonical’s paid Legacy add-on extends maintenance by a further two years, until 2032.
Release End of standard support End of ESM (Ubuntu Pro)
Ubuntu 20.04 LTS 31 May 2025 2030
Ubuntu 22.04 LTS 2027 2032
Ubuntu 24.04 LTS 2029 2034

You can read the details in Canonical’s post on the end of 20.04 support.

Check where you stand

On a server, a few commands show which release is running, and how many packages already get fixes only from ESM:

lsb_release -a
pro status
pro security-status

The output of pro security-status also shows which packages come from the universe repository – even now, not every fix arrives for these without ESM-apps.

Option 1: upgrade to 22.04, then to 24.04

For most servers, this is the right solution. Importantly, you can’t upgrade directly from 20.04 to 24.04: you have to move to 22.04 first, and from there on to 24.04. Both steps work the same way:

sudo apt update && sudo apt full-upgrade
sudo reboot
sudo do-release-upgrade

do-release-upgrade only offers a new LTS if the /etc/update-manager/release-upgrades file contains Prompt=lts – on servers, this is the default.

Before upgrading:

  • Make a backup or a snapshot. For a virtual machine, this is the quickest way back.
  • Review the third-party repositories. The upgrader disables PPAs and third-party sources (for example, the popular ondrej/php PPA or the Docker repository). Afterwards, you have to re-enable them yourself, pointing to the new release’s repositories.
  • Account for the version changes. The table below shows what changes for the most common components:
Component 20.04 22.04 24.04
Linux kernel 5.4 5.15 6.8
PHP 7.4 8.1 8.3
Python 3.8 3.10 3.12
OpenSSL 1.1.1 3.0 3.0
PostgreSQL 12 14 16
MySQL 8.0 8.0 8.0

Moving from PHP 7.4 to 8.x requires code changes for most old PHP applications, and OpenSSL 3.0 disables old encryption algorithms, which can cause problems with old clients or devices. The upgrade doesn’t convert PostgreSQL clusters automatically: you have to move the old cluster to the new version with the pg_upgradecluster command.

On a production server, we work by first running through the whole upgrade on a clone of the snapshot or backup, and only after a successful trial do we move on to the production machine.

Option 2: a new server with 24.04

If the server has been “growing” for years, has lots of manual changes on it, or if you would rather have a clean slate than a two-step upgrade, install a new server with Ubuntu 24.04 LTS (point release 24.04.2 came out in February), and move the services onto it. This is more work, but:

  • the old server stays as a fallback until you are sure everything works,
  • during the move you document what runs on the machine and how it is configured,
  • it’s a good opportunity to describe the configuration with Ansible or another configuration management tool, so that next time will be simpler.

We wrote about what’s new in 24.04 in a separate article.

Option 3: Ubuntu Pro and ESM

If a server can’t be upgraded by the end of May – because an old application only runs on 20.04, or because you have scheduled the migration for later – Ubuntu Pro buys you time. It’s free for personal and small business use on up to five machines; above that, there is an annual fee per machine. You can request the token on the Ubuntu Pro page, and enabling it is a single command:

sudo pro attach <token>
pro status

In the cloud (AWS, Google Cloud, Azure) there are also separate Ubuntu Pro images, for which the cloud provider bills the fee by the hour.

ESM provides security fixes, not new features or newer software versions. It’s for buying time for a well-planned migration, not for leaving 20.04 unchanged for another five years.

Option 4: isolation, if nothing else works

If an application can neither be upgraded nor moved, and you don’t want Ubuntu Pro either, at least isolate it: it shouldn’t be directly reachable from the internet, only the necessary connections should be allowed, and it should be backed up regularly. Sometimes moving the application into a container on a supported host is also a solution, but that doesn’t replace updating the system inside the container either. We described the options for dealing with end-of-life systems in detail in our article on EOL strategies.

Checklist before 31 May

  1. List all your 20.04 servers and virtual machines, including the ones running in the cloud.
  2. Decide for each machine: in-place upgrade, new server, Ubuntu Pro, or decommissioning.
  3. Check which PPAs and third-party repositories they use, and whether there are 22.04 and 24.04 versions of them.
  4. Test the applications with PHP 8.x, Python 3.10/3.12 and OpenSSL 3.0.
  5. Make a backup, and test the restore too.
  6. On critical machines, run through the upgrade on a clone first.

We have collected the other systems that reach end of life in 2025 in our EOL overview for the year. We help with upgrading and migrating Ubuntu servers and with planning the move; you can read about this on the Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch