# 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:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Andro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andro/32/173721_2.png) [@Andro](https://meta.discourse.org/u/Andro)
#### Post date: [January 9, 2026, 2:05pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/1 "2026-01-09T14:05:55Z")

</div>

Help!

Upgraded server to Ubuntu 25.10 due to impending EOL for 25.04. Now when I attempt update Discourse it fails with this error consistently:

 ![image](https://global.discourse-cdn.com/meta/original/4X/b/7/4/b745b852bfc516273ad3d148afcca80d394140a2.png)

What is causing this?

---

<div class="post-metadata">

### Author: ![Andro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andro/32/173721_2.png) [@Andro](https://meta.discourse.org/u/Andro)
#### Post date: [January 9, 2026, 2:19pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/2 "2026-01-09T14:19:36Z")

</div>

Answering my own question. I proceeded to do a git pull and a launcher rebuild app and all is back to normal. I’ll leave the query here in case anybody else hits this issue.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 9, 2026, 4:04pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/3 "2026-01-09T16:04:02Z")

</div>

> [@Andro](#):
>
> Upgraded server to Ubuntu 25.10 due to impending EOL for 25.04

It’s generally recommended to go with the LTS versions so you have to upgrade only once every 5 years. Though for many years I ran the latest available Ubuntu on my desktop/laptop, there’s not much advantage of living on the bleeding edge for a server.

---

<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:05pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/4 "2026-01-09T16:05:54Z")

</div>

> [@pfaffman](#):
>
> upgrade only once every 5 years

isn’t that a stretch? new lts is available every 2 years, but jumping 2 releases at once will be a lot to chew at once no?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 9, 2026, 4:13pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/5 "2026-01-09T16:13:11Z")

</div>

I recommend moving to a new server when it’s time to upgrade as an in-place OS upgrade requires lots of downtime and might have issues. So I mostly don’t move folks to a new server until the 2nd LTS release (i.e., I’ve sites on 22.04 that I’ll upgrade this year, likely waiting until 26.04.1 gets released in the summer.

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).

---

<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.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 9, 2026, 4:47pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/7 "2026-01-09T16:47:20Z")

</div>

> [@itsbhanusharma](#):
>
> 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.

Wow. I guess it’s been a decade or more since I’ve done one of those. I had no idea it was 2-3 minutes of downtime.

> [@itsbhanusharma](#):
>
> most of what I have is colocated hardware with no luxury of spinning up new machines at will.

I’ve got a few of those too. Maybe I’ll try an OS upgrade next time.

Thanks!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [February 8, 2026, 4:47pm UTC](https://meta.discourse.org/t/cannot-update-discourse-after-ubuntu-25-10-upgrade/393079/8 "2026-02-08T16:47:56Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
