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

<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 28, 2022, 6:33pm UTC](https://meta.discourse.org/t/upgrades-via-ui-disabled-and-not-being-re-enabled-after-ssh-upgrade/216016/19 "2022-01-28T18:33:10Z")

</div>

Update: I think this issue with some untracked files \*may have been the problem.  
I removed the files and made sure that the command `git checkout main` succeeded.  
Then I ran `./launcher rebuild app` and it seems to have worked.

AFAICT, as per what @Falco states above, I don’t think it is _actually_ necessary to track `main` in the Discourse repo. When you run `./launcher rebuild app` the script itself will check out the correct branch.

---

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