# 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:** 15

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 26, 2022, 11:45pm UTC](https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016/15 "2022-01-26T23:45:34Z")

</div>

Launcher changes the branch to main from master automatically. Sounds like something was blocking the automatic switch, like pending stash changes.

---

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