We had this 503 error after each login on our older 3.x instance. After a refresh of the page, the session then works fine.

Now we have installed a plain vanilla 4.6.3 and migrated the mongodb.

Surprisingly the 503 issue is happening as well on the new instance.

Setup is with nginx and 3 NodeBB processes on same VM, and Redis cluster

I assume for some weird reason, the nodebb rate limiting kicks in, but strange that this only occurs after each new login, and reproducible.

Any suggestions how to diagnose or how to modify the rate limiting check to be less aggressive (or to exclude logins)?

Thanks Stefan