# Site inaccessible after rebuilding to latest version

**URL:** https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042
**Category:** 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:** 5
**Page:** 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?

---

<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:41am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042/2 "2019-03-31T06:41:19Z")

</div>

Never mind. User error. During the long period of time I hadn’t rebuilt, I edited the app.yml a few times, including commenting out the few let’s encrypt line items. Reverting those changes brought the site back. thanks.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [March 31, 2019, 6:45am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042/3 "2019-03-31T06:45:11Z")

</div>

The high CPU could have been the forced rebake of all posts with images as part of a recent upgrade migration:

> [@User profile images loading slowly, failing to load](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/14):
>
> High CPU is very unlikely to be Avatar related, there was another change that was committed: [https://review.discourse.org/t/feature-force-rebake-of-all-posts-with-images/937](https://review.discourse.org/t/feature-force-rebake-of-all-posts-with-images/937) This can eat up the entire sidekiq queue for a while. It will clear up but depending on your post count it may take a bit.

---

<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:56am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042/4 "2019-03-31T06:56:07Z")

</div>

This post is timely. I have been wondering where some of the images went. Thanks!

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 3, 2022, 10:29am UTC](https://meta.discourse.org/t/site-inaccessible-after-rebuilding-to-latest-version/113042/6 "2022-06-03T10:29:43Z")

</div>


