# Upgrade failed - could use some help to try and fix using SSH **URL:** \ **Category:** Product Support\ **Created:** [March 17, 2019, 8:57pm UTC](https://meta.discourse.org/t/upgrade-failed-could-use-some-help-to-try-and-fix-using-ssh/111869 "2019-03-17T20:57:06Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![asampal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/asampal/32/134300_2.png) [@asampal](https://meta.discourse.org/u/asampal)\ **Post date:** [March 17, 2019, 8:57pm UTC](https://meta.discourse.org/t/upgrade-failed-could-use-some-help-to-try-and-fix-using-ssh/111869/1 "2019-03-17T20:57:06Z")
Yesterday I had an admin message about upgrades. From the web UI, I did the Docker upgrade first and this seemed to go well. After it finished, the upgrade button for Discourse was enabled and I initiated that. At some point something broke and now our site is down. I was on my phone at the time and I didn’t manage to look at the log carefully to see where exactly things broke, before I’m currently pocking around over SSH and about to try `./launcher rebuild app` to hopefully get a better idea about what exactly is the problem in the upgrade. I’ve never done Discourse command-line repair and I want to make sure that I don’t blow away our data. Looking over app.yml, I see that the container is stateless - great - and that all the data is on the host, accessed as a shared volume. I ran `discourse-doctor` and it looks like disk space is not the issue. Will the rebuild app command touch the local data store? --- _[View the full topic](https://meta.discourse.org/t/upgrade-failed-could-use-some-help-to-try-and-fix-using-ssh/111869)._