# Discourse stuck with 504 Gateway Time-Out error and 100% CPU after rebuild

**URL:** <https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794>\
**Category:** Product Support\
**Tags:** server-resources\
**Created:** [February 11, 2026, 1:29pm UTC](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794 "2026-02-11T13:29:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![nickharambee1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nickharambee1/32/530393_2.png) [@nickharambee1](https://meta.discourse.org/u/nickharambee1)\
**Post date:** [February 11, 2026, 2:24pm UTC](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794/5 "2026-02-11T14:24:45Z")

</div>

Thanks. I didn’t realise that I could increase the memory on the droplet and then reverse it (as long as the disk size isn’t changed). I increased the memory temporarily to 8GB and everything started working as expected, with a CPU of 2-5% (see screenshot below), but when I reverted back to 2GB, which has always worked fine on a forum which only has very light use, the same issue returned with 100% CPU (see screenshot). How could I address this issue without permanently increasing the memory?

 ![Screenshot 2026-02-11 at 14.20.40](https://global.discourse-cdn.com/meta/original/4X/f/1/0/f10fae88543c47801a6201bb49cea81c2f93aa55.png)

---

_[View the full topic](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794)._