Help for owners
My server runs an old Ubuntu that is no longer supported
Short answer
Ubuntu LTS releases get five years of standard security maintenance, and Canonical offers longer coverage through Ubuntu Pro. A server past that window stops receiving fixes from the standard channel. Do not upgrade it in place without a backup. Plan a tested move to a supported release.
Does this sound like your situation?
- My server runs Ubuntu 18.04 or 20.04, or another old version.
- A security scan or my host says the system is out of date.
- Installing anything fails because the old packages are gone.
- My developer says it is too risky to touch.
- The PHP or Node version on the server is also very old.
Why does this happen?
Every release has a support window
Ubuntu says LTS releases receive five years of standard security maintenance. When it ends, the standard channel stops sending security fixes for that release.
Confirmed by ubuntu.com
Extended coverage exists but is a separate subscription
Ubuntu says ESM extends LTS security updates to ten years for the Main repository, and Ubuntu Pro offers up to 1five years of coverage with the Legacy add-on. That buys time; it does not update the software on your server.
Confirmed by ubuntu.com
The apps on it are old too
A new system version often means new PHP, database and Node versions, and an old app may not run on them.
Technical detail: PHP warns that null is passed to a built-in function
An in-place upgrade can fail halfway
Upgrading the live machine can leave it half done. A copy tested first is far safer.
What can I do about it today?
- Find out the Ubuntu versionAsk your developer or host. It is one short answer, and every plan starts from it.
- Check its end dateCompare the version with Ubuntu's release table, linked below.
- Make sure a backup exists firstNo upgrade should start before you know a restorable copy exists.
- Do not click upgrade in the host panelA one-click in-place upgrade on a live production server is the risky route.
- List what runs on the serverSites, databases, scheduled jobs and email. This is what must still work afterwards.
When should I bring someone in?
- The release is past its end date and the server holds customer data.
- Nobody knows what is installed on it.
- The app needs an older PHP or Node than the new system offers.
How do I handle it?
- Inventory the serverI list the software, versions, jobs and configuration, so nothing is forgotten.
- Build the new server beside the old oneA clean supported system is built next to the live one, and the app is installed there.
- Test it with a copy of your dataI check logins, forms, payments and scheduled jobs on the copy.
- Switch over with a way backI move traffic once the tests pass, and keep the old server for a tested rollback.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How long does Ubuntu support a release?
Ubuntu states that LTS releases get five years of standard security maintenance, with ESM extending it through Ubuntu Pro.
Is Ubuntu Pro enough?
It keeps security updates flowing for a time, but the app still needs a plan to move to a supported system.
Can the upgrade be done without downtime?
Building a new server alongside the old one keeps the break short, but I do not promise zero downtime.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Deprecated: Passing null to parameter #1 ($string) of type string is deprecatedPHP warns that null is passed to a built-in functionCertbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:A Let's Encrypt certificate did not renew with Certbot