do-release-upgrade dey say no new release found
Server dey show `No new release found.`? Check `Prompt`, LTS point release gate, third-party repos and held packages to find wetin block upgrade.
Why do-release-upgrade talk say e no find new release
do-release-upgrade wey end for No new release found. almost never mean say the tool spoil. The path wey you ask for no open for that time, and the tool report am in the shortest way e fit. Five things fit close am: the Prompt setting for /etc/update-manager/release-upgrades, the point release gate for LTS (long term support) upgrades, third-party repositories, packages wey dem hold or configure only halfway, and a release wey pass its end of support, so its packages don comot from the main archive.
Check dem in that order. Each one get command wey go prove whether e apply to your server, so you no need guess which of the five you dey face.
Wetin the check-only flag dey show exactly
sudo do-release-upgrade -c
echo $?-c na check only. E dey read Canonical release metadata over HTTPS (hypertext transfer protocol secure) and e dey print the answer. E no dey download any upgrade tool and e no dey rewrite any source file. Two outputs dey important:
Checking for a new Ubuntu release
No new release found.Checking for a new Ubuntu release
New release '26.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.For LTS release wey get Prompt=lts, dem dey word the first answer differently. The upgrader source dey print There is no development version of an LTS available. anytime wey Prompt=lts dey set and e no see anything, even if you no pass -d. E mean the same thing as No new release found..
The exit code dey carry the same answer for scripts. E dey 0 when release dey available and 1 when none dey. This one follow the normal shell convention of zero for success, so script fit treat zero exit as "new release dey available".
If your login banner still dey show the old answer, e mean say e dey cached. That line dey come from /etc/update-motd.d/91-release-upgrade, wey dey hand over to /usr/lib/ubuntu-release-upgrader/release-upgrade-motd, and that helper dey work from the text wey dey stored for /var/lib/ubuntu-release-upgrader/release-upgrade-available. If you run the helper yourself, e no go give you fresh answer. Within one day of the last check, e go just reprint whatever text dey stored and e no go ask anything. Once the stored text don reach one day, or when no stored file dey and the helper run as root, e go start /usr/lib/ubuntu-release-upgrader/check-new-release -q for background, write that check output inside the stored file, and e no go print anything. Anyhow, wetin the banner show no be the result of check wey you do for that login. To clear stale banner, delete the stored file with sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available, and the next login go start fresh check. For the answer itself, just trust -c. The banner only dey repeat the result of the last check wey run.
The check also need to reach changelogs.ubuntu.com. For server wey dey behind strict outbound firewall or proxy, the tool no fit ask, so e no fit find anything.
curl -sI https://changelogs.ubuntu.com/meta-release-lts | head -n 1HTTP/2 200 line mean say the server fit see the metadata. If no output show at all, e mean say the request fail, because -s dey hide curl error message, so run echo $? immediately after. Exit code 6 mean say the name no resolve. Exit code 7 (failed to connect) or 28 (timed out) usually point to your egress rules or proxy, even though slow DNS lookup also dey count against curl connect timeout. Anyhow, no amount of editing APT (advanced package tool) files go change the answer.
If the command no dey at all, e dey inside ubuntu-release-upgrader-core. Minimal cloud images sometimes no dey include that package.
sudo apt install ubuntu-release-upgrader-coreRead /etc/update-manager/release-upgrades before you change anything
cat /etc/update-manager/release-upgrades[DEFAULT]
Prompt=ltsThe file get im comments wey explain itself. Three values dey valid:
never: e no go ever check for, and e no go ever allow, upgrade go new release.normal: e go offer the supported release wey follow the one wey dey run immediately.lts: e go offer the first LTS release wey follow the one wey dey run.
Prompt=never na the easiest one to diagnose, because the tool go name both the file and the setting for its output:
Checking for a new Ubuntu release
In /etc/update-manager/release-upgrades Prompt
is set to never so upgrading is not possible.Hosting providers and configuration management tools dey set never deliberately, so release versions for plenty servers no go drift apart. If you see am there, somebody choose am. Change am to lts for server wey you want make e remain for long term support track, then return am to the old value afterwards if your automation dey expect am.
One detail for those comments dey catch people. When Prompt=lts set and the release wey dey run no be LTS release itself, the upgrader dey treat the setting as normal. For 25.10 machine, the two values dey behave the same way. For 24.04 machine, dem dey read different files, and na that difference be the whole point of the next section.
Why upgrade from one LTS to another one dey wait for the first point release
Prompt na im dey decide which metadata file the upgrader go read. The addresses dey inside /etc/update-manager/meta-release:
[METARELEASE]
URI = https://changelogs.ubuntu.com/meta-release
URI_LTS = https://changelogs.ubuntu.com/meta-release-lts
URI_UNSTABLE_POSTFIX = -development
URI_PROPOSED_POSTFIX = -proposedPrompt=lts dey read meta-release-lts. Prompt=normal dey read meta-release. Both files dey describe every release inside small block of keys, and the upgrader go only offer release if e Supported: flag dey set to 1. You fit read dem yourself, from the same server:
curl -s https://changelogs.ubuntu.com/meta-release-lts | grep -A 4 resolute
curl -s https://changelogs.ubuntu.com/meta-release | grep -A 4 resoluteWhen we check for 27 October 2026, the two files agree about Ubuntu 26.04. The LTS file talk say:
Dist: resolute
Name: Resolute Raccoon
Version: 26.04.1 LTS
Date: Thu, 23 April 2026 00:26:04 UTC
Supported: 1The plain file talk say:
Dist: resolute
Name: Resolute Raccoon
Version: 26.04.1 LTS
Date: Thu, 23 April 2026 00:26:04 UTC
Supported: 1Dem no always dey agree. For 13 August 2026, the LTS file still list Version: 26.04 LTS with Supported: 0, while the plain file don carry Supported: 1. That 0 wey dey the LTS file na im be the gate. One 24.04 server wey dey use the default Prompt=lts read that file, e no see any newer LTS release wey dem mark as available, so e report say nothing dey to upgrade to. Nothing wrong with the machine. Canonical never open the path that time.
The flag go flip to 1 when Canonical enable LTS upgrades. This one dey happen after the first point release, no be the same day wey dem release am, and for 26.04, e don happen. Ubuntu 26.04.1 release for 27 August 2026, and for 29 September 2026, Canonical announce say upgrades from 24.04 "don dey enabled". The LTS file now mark 26.04.1 as supported, so if your 24.04 server dey use Prompt=lts, e go see 26.04.1 and the gate no be reason for empty answer again. If your 24.04 server still no see anything, the reason dey another place for this page: maybe cached login banner, blocked access to changelogs.ubuntu.com, or Prompt=never. Point release no be new version of Ubuntu, na just the same release with every update since launch folded into fresh install media, so wetin concern running server na the gate wey dey open after the release, no be the media itself. The delay na intentional: the pipo wey upgrade early go find the blockers, and dem go fix dem before the plenty LTS servers follow. Canonical 26.04.1 announcement talk say the automatic offer through Update Manager go come "a couple of weeks following this release after some planned backports to address regressions in a recent version of rust-coreutils". For the details, what 26.04.1 shipped with and what it means for a 24.04 server continue the story from there.
Now wey the gate open, the old choice between to wait or switch to Prompt=normal no apply to this upgrade again. Leave Prompt=lts as e be and run sudo do-release-upgrade, wey now target the released 26.04.1. If you switch to normal while the gate still close, change the value back to lts so the server go stay on the long term support track. The procedure itself, step by step, dey inside the full 24.04 to 26.04 server upgrade walkthrough. Server wey still dey 22.04 get extra hop to make, because Prompt=lts only dey offer the next LTS release, so the route from 22.04 to 26.04 goes through 24.04 first.
Third party repositories and PPA wey dey block upgrade
The upgrader dey rewrite your APT sources make e point go the new release. By default, e dey keep Ubuntu own archive and mirrors, but e dey comment out third party repositories, even the ones wey don already publish for the new release. One entry wey e keep go still dey disabled if e no get Release file for the new series. The reasons dey inside the upgrader log, one line per entry, instead of the screen, and dem dey specific: was disabled (unknown mirror), was disabled (unknown dist), and was disabled (no Release file).
One PPA (personal package archive) dey publish separately for each Ubuntu series, and many dey publish for several at once. The graphics-drivers PPA, for example, list both noble/ and resolute/ for inside its dists/ directory. One PPA wey the owner never build for resolute yet no get directory for am for the server, so even if you allow third party sources, the upgrader no fit fetch Release file for the new series and e go disable the entry. Open https://ppa.launchpadcontent.net/<owner>/<ppa>/ubuntu/dists/ for browser to see which series your own get. If one series miss, e usually be warning wey you fit accept. E go turn to stop if one package wey you install from that repository no fit move with the rest of the system. APT dey keep one version of each package, wey dem choose by priority based on dependency constraints, and by default, e no dey downgrade package wey you don install. One PPA version wey new pass the one wey the new release get go therefore stay, and if e depend on library versions wey the new release no get again, the upgrade calculation go fail.
Decide this one by yourself before you start, instead of make you allow the tool decide during one long run wey you no dey watch.
ls /etc/apt/sources.list.d/
apt policy nginx
sudo add-apt-repository --remove ppa:example/ppaapt policy on top one package name go print, as the manual talk, "detailed information about the priority selection of the named package": the versions wey APT fit see, the repositories wey their current indexes offer each one, and their priorities. Run am on the packages wey you care about to see which ones the source wey you wan disable currently dey supply. E no be record of where the installed copy come from, and e no talk anything about which other packages depend on am. One installed version wey only PPA offer be strong hint say e come from there, but no be proof. If you remove the source, e no go downgrade anything, so one package wey you install from PPA go stay for its PPA version and fit be newer than wetin the new release get. Where that one matter, remove the package too, and reinstall am from the archive after the upgrade. One repository wey you plan to bring back, like Tailscale, need make you update its codename to the new release before the package go install again, na from there most Tailscale install errors on Ubuntu dey come.
One flag dey for the opposite choice. The manual page describe --allow-third-party as "Try the upgrade with third party mirrors and repositories enabled instead of commenting them out." Use am only when you don confirm say the repository don already publish for the target release. If e no publish, the flag no go help you, because entry wey no get Release file for the new series go still dey disabled, or e go keep packages enabled wey dem never build for that release.
For Ubuntu 24.04 and later, most sources dey live for /etc/apt/sources.list.d/ubuntu.sources for the deb822 format. The same repository wey you write for both old and new format na separate problem. On its own, e only dey produce warning say the target is configured multiple times, but two entries for the same source wey set conflicting options go stop APT with error. Both of dem dey covered for the duplicate source entry error in deb822 format.
Packages wey dey held or only half configured fit stop the calculation
Release upgrade must move almost every package for the system. If one package no fit move, the calculation go fail, and upgrader prefer stop early instead make e leave you halfway. Two commands fit find the cause.
apt-mark showhold
sudo dpkg --auditapt-mark showhold dey print held packages one per line, and e no go print anything for clean system. Hold na manual instruction say make system never change that package. Person fit pin kernel or database version, then forget am. Release the ones wey you no need again with sudo apt-mark unhold followed by the package name.
dpkg --audit dey list packages wey dem unpack but never configure. This state dey come from install wey stop halfway, most times because session disconnect. Upgrader dey try repair am and log dpkg interrupted, calling dpkg --configure -a, but if you run the repair by yourself first, you go read the error instead of searching for am later. If the tool no fit repair package, e go show message Package in inconsistent state. That one need attention before you retry.
Make the release wey dey run fully current before you upgrade am.
sudo apt update
sudo apt full-upgrade -o APT::Get::Always-Include-Phased-Updates=true
sudo apt --fix-broken install
sudo dpkg --configure -a
sudo rebootThe phased updates option matter pass as e first look. Ubuntu dey roll out some updates to percentage of machines at a time, so plain apt upgrade fit correctly leave some packages behind. The server go then be less current than you think. That option dey take all of dem. Reboot afterwards if kernel come with the updates, so you go upgrade from the kernel wey you dey run. Box wey already dey keep itself patched through unattended security upgrades get less work for here, although that mechanism no dey cross release boundary by design.
Wen di release don pass di time wey dem dey support am
Dem dey support interim Ubuntu release for nine months. Wen dat support finish, di Supported: flag go change go 0, but dat one alone no mean say di path don close. Di upgrader dey skip unsupported releases only as target, and di notice wey Canonical release say 25.10 don reach end of life for 9 July 2026 talk say: "Di supported upgrade path from Ubuntu 25.10 na go Ubuntu 26.04 LTS." Wen we check am for 27 October 2026, meta-release talk dis one about 25.10:
Dist: questing
Name: Questing Quokka
Version: 25.10
Date: Thu, 09 October 2025 00:25:10 UTC
Supported: 0Wetin dey close di path na di archive, and e dey move later pass di end of life date. Di same notice talk say dem go move 25.10 go old-releases.ubuntu.com "for di weeks wey dey come". Wen we check am for 27 October 2026, questing still dey for archive.ubuntu.com and e never reach old-releases.ubuntu.com, so 25.10 server fit still update and upgrade straight go 26.04 LTS. Once dem move one release, dem go commot di packages from archive.ubuntu.com and keep am for old-releases.ubuntu.com. Den apt update go start to dey return 404 Not Found, di system no go fit update again, and because di upgrader must see current system, nothing go fit work. Fix di sources first.
lsb_release -cs
grep -rn ubuntu.com /etc/apt/sources.list /etc/apt/sources.list.d/Point both archive.ubuntu.com and security.ubuntu.com go old-releases.ubuntu.com, and leave your codename as e be. Only di host name go change.
sudo sed -i.bak -e 's/archive.ubuntu.com/old-releases.ubuntu.com/g' \
-e 's/security.ubuntu.com/old-releases.ubuntu.com/g' \
/etc/apt/sources.list.d/ubuntu.sources
sudo apt updateRun di same command against /etc/apt/sources.list instead if your server still keep im sources for dat single file. Di -i.bak option dey write backup beside di original one, so you fit put am back if you edit di wrong file. One clean apt update afta dat one mean say di archive dey reachable again, and do-release-upgrade go come talk to you.
Make you dey realistic about how far dis one go carry you. Ubuntu dey support one release step at a time, so if your server dey two or three dead releases behind, you need to do every step one by one, and each step fit fail because of third party repository or package wey dem hold. For VPS, e dey usually faster to build new server for di current LTS, move your service go there, and keep di old one until you sure. Dat one also give you way to rollback, wey in-place upgrade no fit give you. If you dey choose which track you wan follow afta, di difference between LTS and interim releases for server na better tin to read before you decide.
Wetin the development release flag really dey do
-d, or --devel-release, dey add -development go the address of the file wey Prompt select, so the upgrader go read meta-release-development under Prompt=normal and meta-release-lts-development under Prompt=lts. E still dey allow the upgrader pick release wey e Supported: flag still dey 0. The manual page describe am as "If using the latest supported release, upgrade to the development release."
As we check am for 27 October 2026, the newest entry for meta-release-development no be 26.04:
Dist: stonking
Name: Stonking Stingray
Version: 26.10
Date: Thu, 15 October 2026 00:26:10 UTC
Supported: 0But the newest entry no be wetin the upgrader dey pick. E dey follow the file order and e dey take the first release wey date come after the one wey you dey run. For 24.04 server wey dey resolute for both development files, so -d for 24.04 go land for the released 26.04.1, and Canonical own 26.04.1 announcement tell 24.04 users wey "eager to make the jump" make dem run do-release-upgrade -d. Now wey the LTS gate don open, one plain do-release-upgrade go reach the same release even without the flag. For 26.04 server, the first newer entry na 26.10. Ubuntu release 26.10 for 15 October 2026, but as we check am for 27 October 2026, meta-release still dey end for resolute, so 26.04 server wey dey Prompt=normal go get No new release found. from one plain check. Canonical 26.10 announcement talk say users of 26.04 "will be offered an automatic upgrade to 26.10" if dem choose make dem dey notify dem about all releases, but dem no give date. Until that entry show, -d for 26.04 go reach the released 26.10 only through the development file, where e still dey marked Supported: 0, ahead of the path wey Canonical don open. The 26.10 release notes add say systems wey dey run under TPM-backed full disk encryption no fit upgrade from 26.04 to 26.10 for release time. With Prompt=lts for place for 26.04, meta-release-lts-development no go list anything after resolute, and the flag go stop with e own message:
There is no development version of an LTS available.Ubuntu server documentation dey direct about the flag: "using the development release (or the -d flag) is not recommended for production environments". Development release dey change everyday and e no get any promise of security support, so package wey dey work for morning fit break service for afternoon. When -d point go development release, use am for scratch virtual machine wey you build to test your own configuration. Make you no use am for server wey anybody dey depend on. When you want the released 26.04 for 24.04 server, one plain do-release-upgrade with Prompt=lts go carry you reach there now.
Run the upgrade wey SSH session wey cut no go fit spoil
Release upgrade dey replace most parts of the system, including openssh-server and systemd. If your SSH (secure shell) session die while dpkg dey work, dem go kill the process while some packages don unpack but never configure. Na exactly this state dey stop your next attempt. If this don happen to you already, how to recover upgrade wey stop halfway na separate work, and you must do am before any second attempt. Start upgrade inside terminal multiplexer every time.
sudo apt install -y tmux
tmux new -s upgrade
sudo do-release-upgradeIf the connection cut, log back in and run tmux attach -t upgrade. The upgrade go still dey run, because e be child of the tmux server, no be your SSH session. screen -S upgrade and screen -r upgrade dey do the same work if you prefer screen.
The upgrader get im own safety net for pipo wey no dey use multiplexer. When e detect say e dey run under SSH, e go offer to start second sshd for port 1022, so if the main session cut, you go still get way to enter. E dey decide by checking im own parent processes to find one wey dem call sshd. Inside tmux or screen, that check go find the multiplexer server instead, so the offer no go show, and the pid file /var/run/release-upgrader-sshd.pid go only write when the extra daemon actually start. Nothing dey wrong if you no see the prompt. You already get the better protection.
If you accept the offer, the port no go open by itself. The tool go tell you clearly, because to open port na security decision wey the tool no get right to make for you. Open am for the time wey the upgrade go take, then close am back.
sudo ufw allow 1022/tcp
sudo ufw delete allow 1022/tcpMost VPS providers dey run second firewall for dia control panel, outside the operating system. You must open port 1022 for there too, if not, the fallback listener go dey run but you no go fit reach am, and that one na the worst case.
Four things must dey ready before you type the command:
- Take snapshot or full backup. In-place release upgrade no get undo, and na this one be your only chance.
- Confirm say you fit open your provider console before you need am. If the server no come back after e reboot, SSH na the exact thing wey you no go get. Kernel wey fail to boot na different problem wey get im own recovery steps, wey we cover for a VPS that will not boot after a kernel update.
- Check free space with
df -h / /boot. The upgrade dey download full set of packages, and/bootpartition wey keep plenty old kernels na common place wey upgrade fit stall. - Read the release notes for the services wey you dey run. Major version jump for PostgreSQL or PHP go come with the release, whether you plan for am or not.
FAQ
Why does do-release-upgrade say no new release found on Ubuntu 24.04?
The LTS point release gate no be the reason again. Until Canonical enable LTS upgrades for 29 September 2026, about one month after Ubuntu 26.04.1 ship for 27 August 2026, 26.04 carry Supported: 0 for inside https://changelogs.ubuntu.com/meta-release-lts, the file wey the default Prompt=lts dey read, so the tool no see anything. We check am for 27 October 2026 say that flag na 1, and dem dey offer 26.04.1 to 24.04 server. If your own still no see anything, run sudo do-release-upgrade -c instead of to trust the login banner, confirm say the server fit reach changelogs.ubuntu.com, and check say Prompt no dey set to never. With Prompt=lts, the empty answer dey read There is no development version of an LTS available., wey mean the same thing.
Is it safe to set Prompt=normal instead of waiting for the point release?
For 24.04 to 26.04, nothing dey again wey you go wait for. Canonical enable the upgrade for 29 September 2026, after the point release ship for 27 August 2026, and we check for 27 October 2026 say both meta-release and meta-release-lts mark 26.04 with Supported: 1, so Prompt=lts don dey offer am already and you no gain anything if you switch. Before dem enable upgrades, Prompt=normal bin upgrade you go the released 26.04 instead of development build, but the wahala be say you go upgrade before dem fix the blockers wey early upgraders find. If you switch while you dey wait, set the value back to lts.
Does the -d flag upgrade me to 26.04?
From 24.04, yes. -d dey take the first release wey date come after the one wey you dey run, and for both development files, that one na 26.04, wey now be 26.04.1, na why Canonical 26.04.1 announcement tell eager 24.04 users make dem run do-release-upgrade -d. The newest entry for meta-release-development, wey we check for 27 October 2026, na Ubuntu 26.10, wey release for 15 October 2026 but dem still mark am Supported: 0 for there and e no dey listed for meta-release yet, and na there -d dey point from 26.04 server. Ubuntu own server documentation talk say development release (or the -d flag) no be something wey dem recommend for production, and since the LTS gate don open, ordinary do-release-upgrade go reach 26.04.1 without the flag.
apt update returns 404 errors on an old release. How do I upgrade it?
That release don reach end of life, so dem move the packages from archive.ubuntu.com go old-releases.ubuntu.com. Change only the host names for /etc/apt/sources.list.d/ubuntu.sources, or for /etc/apt/sources.list if you dey use older layout, and keep your codename as e be. Then run sudo apt update and sudo apt full-upgrade. Once the system current again, do-release-upgrade fit move am forward one release at a time.
Do I need to remove my PPAs before running do-release-upgrade?
You no need to, because by default the upgrader dey comment out third party sources, join with any source wey no get Release file for the new release, and e dey log one line like was disabled (unknown mirror) for each one. E better make you do am yourself first, because you go choose the order and you go see the result. Run apt policy on the packages wey you care about to see which versions each PPA dey offer currently. APT no dey record where installed copy come from, so treat any installed version wey only PPA dey offer as strong hint, and reinstall those packages from the archive if the PPA version newer pass the one wey the new release carry.