The server is on an end-of-life Ubuntu
No more security updates, apt sources that no longer resolve, and software that quietly stopped getting patched months or years ago.
Brought onto a supported LTS
Running on Ubuntu?
Most Ubuntu boxes that reach us are two or three LTS releases behind, no one is sure what is installed, and the last person to touch them left years ago. We take an honest inventory, patch what we can in place, and plan the upgrade that has been put off for too long.
What it is
Ubuntu is a Debian-based Linux distribution from Canonical Ltd., founded by Mark Shuttleworth and first released in October 2004. It is the operating system behind a very large share of public cloud servers, container base images and developer laptops, and most hosting providers ship an Ubuntu image by default.
Long Term Support releases come out every two years: 16.04 Xenial, 18.04 Bionic, 20.04 Focal, 22.04 Jammy and 24.04 Noble. Standard support runs for five years, with another five years of Extended Security Maintenance available through the paid Ubuntu Pro programme. Day to day it uses apt for packages, systemd for services, and netplan for network configuration.
The honest version
No technology is all upside. This is where Ubuntu Linux earns its place and where it tends to cause trouble.
Sound familiar?
The Ubuntu Linux problems that bring people to us, and what you have once each one is fixed.
No more security updates, apt sources that no longer resolve, and software that quietly stopped getting patched months or years ago.
Brought onto a supported LTS
Services that will not start, a web stack pinned to an old PHP, and a kernel that boots but is missing drivers the previous one had.
Upgrade finished and verified
A single service growing until the kernel kills it, often a database or a worker queue with no limits set.
Sized and limited to fit
Log rotation disabled, old kernel packages piling up, or a Docker install that has never been pruned.
Space reclaimed, alerts in place
A third-party PPA whose signing key expired, or a repository that was removed upstream while still listed in sources.list.
Sources cleaned, updates flowing
Password login left on, the default port exposed, and no rate limiting beyond what fail2ban is doing by itself.
Keys only, surface reduced
unattended-upgrades not installed, or installed and failing quietly behind a broken repository.
Patching on, with reports
Root access through one account nobody remembers, cron jobs of unknown purpose, and no record of what was ever changed from default.
Documented and in your name
What we do
Call us for one failing server, or hand us the whole fleet.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We take a full backup, rehearse the upgrade path on a copy, and then step the server forward one LTS at a time. 18.04 goes to 20.04, then 22.04, then 24.04 if that is where you want to land. Where an in-place upgrade is riskier than a rebuild, we say so and move you onto a fresh server instead.
Yes, that is a large part of what we do. We inventory what is running, rotate the credentials, document the services and cron jobs, and give you back a system where you know who has access and what each box is for.
Usually a package that was pinned to an old version, a PPA that has no release for the new Ubuntu, or a service whose configuration format changed between versions. These are all recoverable, and all easier to catch on a rehearsal than on the live server.
unattended-upgrades can apply security patches on its own, with the right allow-lists and a sensible reboot policy. We configure it to email when it runs, hold back packages that need manual review, and reboot in a window you choose rather than at random.
Upgrading is almost always the better answer. Ubuntu Pro buys you more time on an old release, which is useful when a real upgrade cannot be scheduled this quarter, but it does not fix the fact that the software on the box is ageing. We will tell you plainly which path fits your situation.
Estimates are free. Tell us what the servers are doing and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: