# Site went down after upgrading Discourse .xx11
**URL:** https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582
**Category:** Self-hosting
**Created:** [7월 21, 2016, 5:46오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582 "2016-07-21T05:46:55Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Rodelio\_Lagahit](https://meta.discourse.org/u/Rodelio_Lagahit)
#### Post date: [7월 21, 2016, 5:46오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/1 "2016-07-21T05:46:55Z")
Site went down after upgrading Discourse .xx11
Just updated the site (hrm.com.ph), but after successfully updating, it’s no longer accessible. but I can access the /admin/upgrade page still.
tried rebuild app, still to no avail.
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [7월 21, 2016, 5:50오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/2 "2016-07-21T05:50:25Z")
> [@Rodelio\_Lagahit](#):
>
> hrm.com.ph
Looks up for me. What are the symptoms you’re seeing? What do your logs say?
---
### Author:  [@Rodelio\_Lagahit](https://meta.discourse.org/u/Rodelio_Lagahit)
#### Post date: [7월 21, 2016, 5:54오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/3 "2016-07-21T05:54:48Z")
it’s plain white from my end.
ill check the logs
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [7월 21, 2016, 5:59오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/4 "2016-07-21T05:59:12Z")
Oooh, the plot thickens…
It loads fine as a static HTML page, but when I enable JS, the page goes blank. Console sez:
```
_ember_jquery-c9524b4….js:46239 Uncaught Error: Could not find module `discourse/lib/emoji/emoji-toolbar` imported from `discourse/plugins/babble/discourse/widgets/babble-composer`
```
I’m thinking you might need to update or disable the babble plugin, because it appears to be making things sad.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [7월 21, 2016, 6:04오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/5 "2016-07-21T06:04:01Z")
This is, yet again, why we need an easy “[safe mode](https://meta.discourse.org/t/53504?silent=true)” that disables all plugins for Discourse 1.7 [@team](https://meta.discourse.org/groups/team)
---
### Author:  [@Rodelio\_Lagahit](https://meta.discourse.org/u/Rodelio_Lagahit)
#### Post date: [7월 21, 2016, 6:25오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/6 "2016-07-21T06:25:32Z")
yep, disabling it now.
got it. I think it’s the babble chat. it’s working fine now.
@gdpelican, this might be helpful to you.
---
### Author:  [@gdpelican](https://meta.discourse.org/u/gdpelican)
#### Post date: [7월 21, 2016, 6:32오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/7 "2016-07-21T06:32:52Z")
Looks like an old version of Babble, that’s been fixed in the latest.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [10월 8, 2023, 7:47오전 UTC](https://meta.discourse.org/t/site-went-down-after-upgrading-discourse-xx11/47582/8 "2023-10-08T07:47:01Z")