# Multisite upgrading seems stuck with black box empty

**URL:** https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047
**Category:** Support
**Created:** [February 4, 2022, 3:48am UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047 "2022-02-04T03:48:07Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jimkleiber](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimkleiber/32/121814_2.png) [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [February 4, 2022, 3:48am UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047/1 "2022-02-04T03:48:07Z")

</div>

I’ve recently installed multisite on a 2GB RAM DO droplet with 6 sites. I think I should probably use a higher RAM option and yet since all forums will be really small for the start, was hoping I could start cheap.

Regardless, when I go to upgrade from the admin page of any of the forums, including the main/default forum, when I click on the blue upgrade button, the button turns to gray and says “Upgrading…” but then I don’t see anything appear in the black terminal box below, as I would normally see on my single-site installations.

 ![image](https://global.discourse-cdn.com/meta/original/3X/a/4/a44c2465b12928bf1afcd675afead1252f9c4e3f.png)

It has been at least 10-15 minutes now and I still don’t see anything and am unsure if it’s making any progress.

- Any idea why this might be happening?
- Am I able to upgrade from any of the forums’ UIs?
- If not, do I have to upgrade the multisite from the command line?

Edit: I reset the upgrade, waited a bit, refreshed the page, and tried to upgrade the Discourse Assign plugin and then info showed in the box that I didn’t have enough unicorn workers, I think from the previous upgrade. I clicked upgrade for that plugin and it worked, so I’m assuming the problem was that I just don’t have enough RAM, as per this [How to avoid upstream timeouts? - #2 by mpalmer](https://meta.discourse.org/t/how-to-avoid-upstream-timeouts/35483/2)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 4, 2022, 11:07am UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047/2 "2022-02-04T11:07:07Z")

</div>

You’ve said at least twice that you don’t have enough ram. I think you’re right. Have you considered increasing the amount I ram?

---

<div class="post-metadata">

### Author: ![jimkleiber](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimkleiber/32/121814_2.png) [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [February 4, 2022, 8:04pm UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047/3 "2022-02-04T20:04:15Z")

</div>

Ah, I know I’ve thought about not having enough RAM, but I’m pretty sure this was the first time that I posted about it—but maybe not.

After I found the problem here was the lack of memory, I thought about deleting the topic but thought maybe it’d be helpful to leave it up for people in case they encounter a similar bug.

While I had read about different RAM recommendations, ranging from:

> [@Server specs for multisite](https://meta.discourse.org/t/server-specs-for-multisite/29920/3):
>
> I would not recommend that, no. I’d say 512mb ram _minimum_ for each additional community.
> 
> So 1 GB to start with community 1, then + 512mb for community 2, + 512mb for community 3, etc.

and

> [@I want to host hundreds of instances of Discourse](https://meta.discourse.org/t/i-want-to-host-hundreds-of-instances-of-discourse/133388/8):
>
> I don’t recommend going multisite with \< 4GB of ram, but [Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084).

I had not read much about the ramifications of not having enough RAM. I was seeing that the sites are slower but with this I saw that rebuilds/upgrades can fail because of not enough memory.

I was going to be OK with slower sites for now to save the $10/month, but failing upgrades annoy me enough, so I’ll bump up the memory.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 5, 2022, 2:20am UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047/4 "2022-02-05T02:20:41Z")

</div>

If you leave the disk the same size you can scale it back down later (if ram isn’t the issue somehow).

---

<div class="post-metadata">

### Author: ![jimkleiber](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimkleiber/32/121814_2.png) [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [February 5, 2022, 2:34am UTC](https://meta.discourse.org/t/multisite-upgrading-seems-stuck-with-black-box-empty/217047/5 "2022-02-05T02:34:37Z")

</div>

Yeah that’s what I was planning to do. I noticed just upgrading the ram/CPU will give me the same price as upgrading with the larger disk as well, but would prefer the reversible ram/CPU option for now and if I find that it works or a higher level that works, then I may upgrade with the added disk space (if possible at the same price) or start a new droplet and recreate them there.

@pfaffman, I’m really grateful for your help, your words, and so much that you’ve done on Meta to make it easier for someone like me to install and manage—thank you.
