# Upgrades via the web UI are disabled until you run the latest image

**URL:** <https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-until-you-run-the-latest-image/73122>\
**Category:** Product Support\
**Created:** [Outubro 31, 2017, 12:18pm UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-until-you-run-the-latest-image/73122 "2017-10-31T12:18:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dax](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dax/32/244677_2.png) [@dax](https://meta.discourse.org/u/dax)\
**Post date:** [Outubro 31, 2017, 1:52pm UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-until-you-run-the-latest-image/73122/2 "2017-10-31T13:52:47Z")

</div>

Generally the update via GUI is automatically disabled when the `docker_manager` needs to be updated first.  
When you update via GUI the `docker_manager` you need to run the `./launcher rebuild app` command to rebuild your discourse site, but because you have to do that, in this case is more profitable if you upgrade all (docker + plugins) directly via SSH.

For example, I always update from GUI, after finishing the updates I do the docker restart. When I see that the `docker_manager` want the update I do that via SSH, skipping the update via GUI, because my site goes offline for a few minutes anyway.

---

_[View the full topic](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-until-you-run-the-latest-image/73122)._