Due to extreme load, this is temporarily being shown to everyone as a logged out user would see it

We had a surge of new visitors this morning due to a popular AMA and many people received this message which was somewhat understandable since one topic was getting overloaded and the cpu spiked during this time. Since then it has subsided but I keep getting this error telling me I’m logged out then it refreshes and shows the warning message.

FYI I have 2gb memory and 1 cpu on DO. There were about 30 users online this morning when it first happened and now there are only 10. Do I just need more CPU power or does this seem a bit odd that it keepshappening?

1 Like

How long has the warning gone on? Have you tried restarting the Discourse Docker container and/or server?


It’s been off and on, I have seen it four times today but most of the time it works fine. I just restarted docker using service docker restartis that correct? If it keeps happening I’ll try rebooting, trying to avoid the downtime since we have a lot of new users checking out the site. Thanks Jeff.


It should come back automatically, @sam built this feature and I know it has worked for us in the past as designed… maybe he has some ideas?


Even if there are only 10 users online a large number of users could be doing background work and an enormous of anon users could still be hitting it.

The site should auto recover as soon as the load subsides.

If you really would like to rush it you could try restarting the container.


I has same problem

Use online 5

My server

Disable all your third-party plugins, rebuild, and see if the problem persists. That’s the first step.


@davidkingham You use the browser?

I am having this message too. Could you please explain what condition triggers this message from Discourse? Is it when all Unicorn workers are busy? Some server metrics? Thanks.

Have you tried the steps Jeff and Sam mentioned to resolve it?

Will do, but I nevertheless would like to understand what is being monitored and would appreciate an answer to my question.



Amount of time it takes a request to find its way from NGINX to the Unicorn worker process.


Thanks, @sam, that is very helpful. Now I better understand why a plugin (which is making too many ajax calls) could be causing the problems we are seeing on our site. Besides the “extreme load” message, we are also seeing white “slow down” screens (too many requests, nginx), which would also fit into the picture.

We are now in the process to identify the culprit. One problem we already found is Babble. Our chat was well over 10k posts, which was causing heavy load on the system:

I’ll report back once we know more.