# Cannot update Discourse after Ubuntu 25.10 upgrade

**URL:** <https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079>\
**Category:** Self-hosting\
**Created:** [January 9, 2026, 2:05pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079 "2026-01-09T14:05:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)\
**Post date:** [January 9, 2026, 4:29pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/6 "2026-01-09T16:29:26Z")

</div>

> [@pfaffman](#):
>
> an in-place OS upgrade requires lots of downtime

I’ve done quite a few of them on ubuntu, and barely ever had a site out of comission for more that 2-3 minutes. Granted I’ve tested the process on staging to ensure there are no blockers but managing a fleet of two dozen or so servers justifies the extra steps.

> [@pfaffman](#):
>
> Moving to a clean install requires zero downtime (especially if you can do it with a static ip that gets moved to the new server once it’s writing) working).

That’s a good strategy but only works on systems that have that option, most of what I have is colocated hardware with no luxury of spinning up new machines at will.

---

_[View the full topic](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079)._