# Site is Down after upgrade

**URL:** https://meta.discourse.org/t/site-is-down-after-upgrade/52417
**Category:** Support
**Created:** [11월 3, 2016, 5:18오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417 "2016-11-03T05:18:49Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![LastDance](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lastdance/32/121324_2.png) [@LastDance](https://meta.discourse.org/u/LastDance)
#### Post date: [11월 3, 2016, 5:18오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417/1 "2016-11-03T05:18:49Z")

</div>

My site gives me back a http 500 error after I attempted to upgrade from 17beta6 to 17beta7, and while docker still comes up, Im guessing that means it broke somehow and i need to restore from a backup. (So naturally i did the dumbest thing thing and didnt back up this time).

Before i do though, im going to ask the hopeless but also hopeful question: Is there a way to restore my discourse instance without having to restore from backup?

---

<div class="post-metadata">

### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [11월 3, 2016, 5:38오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417/2 "2016-11-03T05:38:39Z")

</div>

Can you ssh into your server and run the following commands?

```plaintext
cd /var/discourse
./launcher logs app

```

Let us know if you see anything weird in the logs 🙂

---

<div class="post-metadata">

### Author: ![LastDance](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lastdance/32/121324_2.png) [@LastDance](https://meta.discourse.org/u/LastDance)
#### Post date: [11월 3, 2016, 5:45오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417/3 "2016-11-03T05:45:01Z")

</div>

What classifies as weird?

I get a lot of these toward the end:

 ![](https://global.discourse-cdn.com/meta/original/3X/f/7/f7e5f44bdbcc1bf6ded900fc2634b2702f497cc6.png)

and before that, i see this:

 ![](https://global.discourse-cdn.com/meta/original/3X/e/f/ef2b034c1140c88eca8dcc15896f58ede6ffc779.png)

Also, thank you for the quick reply and willingness to help 😅

---

<div class="post-metadata">

### Author: ![LastDance](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lastdance/32/121324_2.png) [@LastDance](https://meta.discourse.org/u/LastDance)
#### Post date: [11월 3, 2016, 6:05오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417/4 "2016-11-03T06:05:51Z")

</div>

Well, i rebuilt the app, and that solved the problem. Sorry for any time of yours i wasted with this 😕

---

<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: [11월 3, 2016, 7:19오전 UTC](https://meta.discourse.org/t/site-is-down-after-upgrade/52417/5 "2016-11-03T07:19:53Z")

</div>