# Multiple Discourses, multiple containers, one server

**URL:** https://meta.discourse.org/t/multiple-discourses-multiple-containers-one-server/35367
**Category:** Self-hosting
**Created:** [November 9, 2015, 3:45am UTC](https://meta.discourse.org/t/multiple-discourses-multiple-containers-one-server/35367 "2015-11-09T03:45:16Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![lightweight](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lightweight/32/116381_2.png) [@lightweight](https://meta.discourse.org/u/lightweight)
#### Post date: [November 26, 2015, 11:19pm UTC](https://meta.discourse.org/t/multiple-discourses-multiple-containers-one-server/35367/3 "2015-11-26T23:19:51Z")

</div>

Ok, looks like the CSS 404s was not “fixed” by disabling SSL for one of the sites - it still periodically stops serving on either/both of the sites. A restart of the web container for either instance will temporarily reinstate the CSS. Seems to be a problem of the CSS aggregation or static file serving… I’ve posted about it here: [https://meta.discourse.org/t/intermittent-stylesheet-errors-on-heroku-installation/26261/12](https://meta.discourse.org/t/intermittent-stylesheet-errors-on-heroku-installation/26261/12)

I should note that I’m not aware of this problem (of 404s for CSS) arising prior to the introduction of the second discourse instance.

---

_[View the full topic](https://meta.discourse.org/t/multiple-discourses-multiple-containers-one-server/35367)._