# Upgrades via UI disabled - and not being re-enabled after SSH upgrade

**URL:** <https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016>\
**Category:** Self-hosting\
**Created:** [January 26, 2022, 12:58am UTC](https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016 "2022-01-26T00:58:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pacharanero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pacharanero/32/500583_2.png) [@pacharanero](https://meta.discourse.org/u/pacharanero)\
**Post date:** [January 26, 2022, 2:07pm UTC](https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016/3 "2022-01-26T14:07:51Z")

</div>

It has puzzled me on occasion when the GUI update doesn’t seem to be reset and it directs us to SSH in, even when this has just literally been done.

It was a [standard install](https://meta.discourse.org/t/142537?silent=true), but the original install was way back in 2014, in the very early days when Discourse was not long out of public beta.

```plaintext
user@server:/var/discourse$ docker -v
Docker version 19.03.13, build 4484c46d9d

```

There is a more recent version of Docker, but it’s common for the version in Ubuntu to lag a little behind the latest.

OS is fully and regularly updated.

---

_[View the full topic](https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016)._