# Upgrades via the web UI are disabled...even after a pull+rebuild

**URL:** <https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836>\
**Category:** Support\
**Created:** [2016年二月1日 16:18 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836 "2016-02-01T16:18:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougluce](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dougluce](https://meta.discourse.org/u/dougluce)\
**Post date:** [2016年二月1日 16:18 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/1 "2016-02-01T16:18:56Z")

</div>

I first got the “Upgrades via the web UI are disabled until you run the latest image” message after attempting a web upgrade. No problem, I follow the instructions. Going back to /admin/upgrade – same message. What might be up?

[- · GitHub](https://gist.github.com/989cd7044d7c73fee0cd) is the install log from the rebuild. Git reports my /var/discourse head at 81195ac66.

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [2016年二月1日 17:42 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/2 "2016-02-01T17:42:23Z")

</div>

That is the correct head. Perhaps @sam can join in here and offer a suggestion as I believe he wrote that code.

---

<div class="post-metadata">

**Author:** ![dougluce](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dougluce](https://meta.discourse.org/u/dougluce)\
**Post date:** [2016年二月3日 15:12 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/3 "2016-02-03T15:12:34Z")

</div>

Is there recommended nuclear option for rebuilding that’s relatively straightforward?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2016年二月3日 23:05 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/4 "2016-02-03T23:05:00Z")

</div>

what is your container config yaml?

---

<div class="post-metadata">

**Author:** ![dougluce](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dougluce](https://meta.discourse.org/u/dougluce)\
**Post date:** [2016年二月3日 23:22 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/5 "2016-02-03T23:22:20Z")

</div>

Turns out I was SSHing into a different machine than I was refreshing  
in my browser. No wonder destroying all the containers and rebuilding  
from scratch had no effect.

Sorry about that!

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2016年二月3日 23:28 UTC](https://meta.discourse.org/t/upgrades-via-the-web-ui-are-disabled-even-after-a-pull-rebuild/38836/6 "2016-02-03T23:28:21Z")

</div>