Having rebuilt discourse today, the CPU on my droplet is stuck at 100% and I am getting a 504 Gateway Time-out error. In terminal I have checked which processes are causing the issue and this is what I see: [Screenshot 2026-02-11 at 13.19.56] So it appears to be an issue with docker and a pitchfork command. Could someone help me understand what might be going on here and how I can address it. I have tried rebuilding the app again and restarting the droplet and still have the same issue.

Does upgrading your Droplet’s specs help?

How long have you waited on this state? We moved to a new webserver today, and sometimes it takes a little longer to fully boot.

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]

I’ve waited 30 minutes or more.

We’ve just merged a change that should fix the issue: https://github.com/discourse/discourse/commit/7324b327cdf72c2e468d33ce35074f5d1c78fe6f It should land in latest shortly, could you try updating your droplet when the fix is available?

Sure. When can I know when it’s ready?

You can check Commits · discourse/discourse · GitHub to see if the commit is in the list. Otherwise, I’ll let you know when I see it’s ready :slight_smile:

OK, thanks for letting me know.

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

Product Support

nickharambee1 February 11, 2026, 2:55pm 12

Thanks. Everything’s working now with 2GB of memory.

Topic		Replies	Views
Emergency help - freeCodeCamp Discourse down Self-hosting	18	2520	February 22, 2017
Discourse stopping working - CPU/RAM load? Product Support	7	1241	September 8, 2019
CPU, Memory and Swap at 100% Self-hosting server-resources	6	789	November 8, 2021
504 Gateway Time-out errors with 2 million post migrated vBulletin forum Self-hosting	3	1190	January 4, 2019
Server not response (DO SGP1) Self-hosting	15	2477	May 17, 2016

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

Related topics