# Multi-site upgrade leaves \_some\_ sites unavailable

**URL:** <https://meta.discourse.org/t/multi-site-upgrade-leaves-some-sites-unavailable/193509>\
**Category:** Product Support\
**Created:** [June 11, 2021, 10:12am UTC](https://meta.discourse.org/t/multi-site-upgrade-leaves-some-sites-unavailable/193509 "2021-06-11T10:12:33Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)\
**Post date:** [June 11, 2021, 10:12am UTC](https://meta.discourse.org/t/multi-site-upgrade-leaves-some-sites-unavailable/193509/1 "2021-06-11T10:12:33Z")

</div>

With the recent upgrade frenzy, leading to 2.8.0.beta2, something strange happened that I’m currently investigating. The effect is that on a multi-site install, _some but not all_ secondary sites do not respond anymore. The primary site is up, and some secondary sites operate normally.

~~I suspect it may have to do with the [discourse-calendar](https://meta.discourse.org/t/discourse-calendar/97376/234) issue already reported on stable, but that’s just a hunch.~~

---

_[View the full topic](https://meta.discourse.org/t/multi-site-upgrade-leaves-some-sites-unavailable/193509)._
