# Updates blocked must run latest img - Discourse hosted

**URL:** <https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674>\
**Category:** Product Support\
**Tags:** hosted-support\
**Created:** [October 25, 2026, 12:25pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674 "2026-10-25T12:25:22Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 25, 2026, 12:25pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/1 "2026-10-25T12:25:22Z")

</div>

Updates via the web UI are disabled until you run the latest image. To do so log in to your server using SSH and run.

This is a discourse hosted forum.

---

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [October 25, 2026, 12:30pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/2 "2026-10-25T12:30:05Z")

</div>

It’s fairly normal that the web UI updates cannot always do the job. So one must always be ready to login and do a command line update.

(One must also always take a backup before an update!)

---

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 25, 2026, 12:32pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/3 "2026-10-25T12:32:10Z")

</div>

how would i do that on discourses servers? I wouldnt think they would allow this.

---

<div class="post-metadata">

**Author:** ![nickdb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nickdb/32/444510_2.png) [@nickdb](https://meta.discourse.org/u/nickdb)\
**Post date:** [October 25, 2026, 12:36pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/4 "2026-10-25T12:36:15Z")

</div>

Can’t you control that in the UI by following the right update channel?

 ![IMG_7936](https://global.discourse-cdn.com/meta/original/4X/d/3/2/d329a336a0f85697412b67cd666b02e3e78730fb.jpeg)

---

<div class="post-metadata">

**Author:** ![Andrew\_Rowe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andrew_rowe/32/445877_2.png) [@Andrew\_Rowe](https://meta.discourse.org/u/Andrew_Rowe)\
**Post date:** [October 25, 2026, 12:58pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/5 "2026-10-25T12:58:31Z")

</div>

> [@Giantkin\_1](#):
>
> This is a discourse hosted forum.

I believe you will get some help shortly

---

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 25, 2026, 1:04pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/6 "2026-10-25T13:04:58Z")

</div>

no rush, i figured i should ask the Founders if the server is self hosted, just in case.

My conversations from years back led me to believe it wasnt. but now…

(it says at the bottom of every page ‘powered by discourse’ )

course, that could mean either way too.

ill find that out before i continue 🙂

---

<div class="post-metadata">

**Author:** ![Andrew\_Rowe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andrew_rowe/32/445877_2.png) [@Andrew\_Rowe](https://meta.discourse.org/u/Andrew_Rowe)\
**Post date:** [October 25, 2026, 1:09pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/7 "2026-10-25T13:09:03Z")

</div>

oh, all installations of Discourse have that ‘powered by discourse’ link at the bottom. If your site is self hosted you will need the ability to log into your server using a secure shell (SSH) where Discourse lives and run the upgrade from the command line

---

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [October 25, 2026, 1:22pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/8 "2026-10-25T13:22:22Z")

</div>

> [@Giantkin\_1](#):
>
> how would i do that on discourses servers?

Oops, I did not take that into account. However, as noted, most likely you are in fact self-hosted.

(You might not necessarily need ssh as your hosting provider might provide you with a web-based command line or console.)

---

<div class="post-metadata">

**Author:** ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)\
**Post date:** [October 25, 2026, 2:25pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/9 "2026-10-25T14:25:20Z")

</div>

I added the #hosted-support tag for clarity. @Giantkin_1 It’s currently the weekend for most, so you’d need to wait until Monday for this to receive support from the team.

---

<div class="post-metadata">

**Author:** ![fuse](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fuse/32/221005_2.png) [@fuse](https://meta.discourse.org/u/fuse)\
**Post date:** [October 25, 2026, 2:31pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/10 "2026-10-25T14:31:01Z")

</div>

Completely tangential, this is my “least favorite” feature of discourse.

I understand the stated logic behind it, and getting self hosted forums also taking care of underlying OS patching.

My curiosity is whether or not there is a technical reason why updates from the UI are disabled, or if its just a pattern to be a pattern.

Flipping it around- I love the ability to update my forum within the mobile app, it makes keeping up with updates simple and convenient.

---

<div class="post-metadata">

**Author:** ![nickdb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nickdb/32/444510_2.png) [@nickdb](https://meta.discourse.org/u/nickdb)\
**Post date:** [October 25, 2026, 2:34pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/11 "2026-10-25T14:34:13Z")

</div>

> [@fuse](#):
>
> I love the ability to update my forum within the mobile app, it makes keeping up with updates simple and convenient.

As a discourse hosted site, we’re quite happy to hand-off that responsibility to team discourse. Their support is top-notch and we can focus on the community and not doing version control.

---

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 25, 2026, 2:38pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/12 "2026-10-25T14:38:36Z")

</div>

Well overall its odd, all the updates for the last 5 years i been able to do, but suddenly blocked and have to ssh in, i thought was weird.

but i asked the website team now, see when that gets answered.  
then, if they say its self, i’ll beg them to update hehe

if its Discourse hosted, ill come back and beg to get updated 😉

lol

---

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [October 25, 2026, 3:51pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/13 "2026-10-25T15:51:07Z")

</div>

You won’t have that update UI on hosted instances at all, so you must be self-hosted or someone is doing that for you.

---

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 25, 2026, 5:33pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/14 "2026-10-25T17:33:17Z")

</div>

yup. i had just clicked update for something from july The new update wouldnt let me do it, i assumed that the july one had to go first. so updated that one just fine. no problems at all.

guess its been over 5yrs for the image version update. well, i got the query in to the team. see what they say/whos doing it.

---

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [October 25, 2026, 6:05pm UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/15 "2026-10-25T18:05:22Z")

</div>

If you hadn’t yet got the big database version update, then picking that up does require you to do two command line updates. Thats from pg15 to pg18, available from early August. See

> [@PostgreSQL 18 update for self-hosters](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194):
>
> warning WARNING! The upgrade requires a lot of free disk space (2x database size). We’ve just landed changes to upgrade our Docker image to PostgreSQL 18. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 18 from the previous PostgreSQL 15. Note that if you held back from upgrading when the PostgreSQL 15 update [happened back in 2025](https://meta.discourse.org/t/postgresql-15-update/349515), you can skip that upgrade and go straight to PostgreSQL 18. If you had held back the upgrade previously, change the …

---

<div class="post-metadata">

**Author:** ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)\
**Post date:** [October 26, 2026, 1:28am UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/16 "2026-10-26T01:28:25Z")

</div>

@Giantkin_1 Could you send a link to your forum if possible? Perhaps I can check if it’s self-hosted or not.

---

<div class="post-metadata">

**Author:** ![Giantkin\_1](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@Giantkin\_1](https://meta.discourse.org/u/Giantkin_1)\
**Post date:** [October 26, 2026, 1:57am UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/17 "2026-10-26T01:57:21Z")

</div>

> **[Giveth Forum: Join the conversation to shape the Future of Giving](https://forum.giveth.io/)**
>
> Read about the inner workings of Giveth on our forum, learn about pending and passed proposals, and join us in open debates. We'd love to hear your voice!

---

<div class="post-metadata">

**Author:** ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)\
**Post date:** [October 26, 2026, 2:19am UTC](https://meta.discourse.org/t/updates-blocked-must-run-latest-img-discourse-hosted/415674/18 "2026-10-26T02:19:09Z")

</div>

Ok; I’m about 95% sure you’re self-hosted. Your site doesn’t use the Discourse CDN for assets, and the `nslookup` command doesn’t have `hosted-by-discourse.com` in your CNAME records.

```plaintext
natedhaliwal@DESKTOP:~$ nslookup ndknowledgebase.discourse.group
Server: 10.255.255.254
Address: 10.255.255.254#53

Non-authoritative answer:
ndknowledgebase.discourse.group canonical name = ndknowledgebase.hosted-by-discourse.com.
Name: ndknowledgebase.hosted-by-discourse.com
Address: 184.105.99.43
Name: ndknowledgebase.hosted-by-discourse.com
Address: 2602:fd3f:3:ff01::2b

```

vs:

```plaintext
natedhaliwal@DESKTOP:~$ nslookup forum.giveth.io
Server: 10.255.255.254
Address: 10.255.255.254#53

Non-authoritative answer:
Name: forum.giveth.io
Address: 64.225.108.97

```

Do you know where your forum is hosted? DigitalOcean perhaps?
