# Site inaccessible after rebuilding to latest version

**URL:** <https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042>\
**Category:** Product Support\
**Created:** [March 31, 2019, 6:04am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042 "2019-03-31T06:04:53Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ckshen](https://avatars.discourse-cdn.com/v4/letter/c/ad7895/32.png) [@ckshen](https://meta.discourse.org/u/ckshen)\
**Post date:** [March 31, 2019, 6:04am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042/1 "2019-03-31T06:04:53Z")

</div>

Hi,

I just rebuilt the container. The rebuilding completed and seemed to have gone fine. I updated from 2.1.xx to the latest 2.3.xx. Afterwards when I try to access the forum, all it says is

> This site can’t be reached
> 
> The webpage at **[https://www.hungryonion.org/](https://www.hungryonion.org/)** might be temporarily down or it may have moved permanently to a new web address.

The container started. Site doesn’t run in [safe mode](https://meta.discourse.org/t/53504?silent=true). Nor can I load the sidekiq page. Rebuilding without plugins yields the same result.

CPU usage is consistently at or near 100% after rebuilding.

 ![image](https://global.discourse-cdn.com/meta/original/3X/5/5/551f5e39f6d72a2a6d83dcb9e4547b7ee16eac1f.png)

Any ideas? I have never encountered this before. The site is hosted on Digital Ocean.

Does skipping rebuilding for many versions have something to do with this issue?

---

_[View the full topic](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042)._