1
503 error after each login (community.nodebb.org)
submitted 8 months ago* by to c/general-discussion@community.nodebb.org
16 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 8 months ago

We do not have any traffic right now, nodeBB is runnning with 3 processes each < 1% CPU% and with traffic management enabled and the standard settings we get the 503 once after login. With traffic management disabled the 503 does not happen.

Can I enable some more debugging/tracing to see why traffic management shuts down the session after login?

  • permalink
  • fedilink
  • source
    •