Pagination may be a bad idea because we make the categories sortable on this list.
I not understand, but thanks, you everytime help for me. I created issue.
If you frequently refresh pages now are redirected to this page public/503.html
But the page is displayed not only the client, which reloads the site, and all users?
If this is so, but any malicious user can interfere with the site, just updating it (F-5).
Am I wrong?
It should be client sided only. However, you can disable it somewhere in the AdminCP by simply setting the time a refresh can take place to 0ms.
@AOKP Strange. It seems to me that it appears at all users.
I updated the page on a computer until the appearance of the page and at has gone site with the other computer - page 503 was there.
@xen well, it could be that it is connection sided then. However, for my site with more than 600 concurrent connections no one else saw it.
@xen Toobusy determines whether the server is behind on requests by checking the "event loop lag". In short, the busier the server, the higher the event loop lag.
The 503 page should only appear to users if the event loop lag increases past a set threshold, which usually manifests itself (withotu toobusy) as a "slow" server taking longer than normal to respond to requests.
You can tweak the threshold value up if you'd like, in order to give the server more leeway.
I am facing the same problem. Everything works fine except that users are very often having the 503 page. I tried the @AOKP solution by setting to 0ms. Since it did not work, I set both setting (loop lag and check interval) to 80000 but the 503 page showed up anyway at a moment where almost no user is browsing. I thought putting so high values was almost equivalent to disable it. I was wrong. So my question : is there a way to simply disable it ? Before, the users never complained about a laggy browsing so I would not expect this to happen in the first place.
@hukadan you are sure that NodeBB has the correct permissions? Did you also tried to reload/restart after applying the solutions?
@AOKP Thank you for your reply
you are sure that NodeBB has the correct permissions
I did not get that part. To which permissions are you referring to ?
Did you also tried to reload/restart after applying the solutions ?
Reload yes. Restart no.
Anyway, I had too many issues with this
toobusy module. I set it to
false in the
middleware.js file. I will reactivate it when I have the time to play around with the different settings.
@hukadan I have no idea how you can even trigger toobusy. On my dev environment, I'm hammering the f5 key and am not getting it to show up anyway.
In any case, I'm testing a new ACP switch to disable, similar to you adding
false to that conditional.
@julian Yep. Given the few people having this problem here, I assume there is a problem on my side. But I could not find which one. The
false setting solution is only temporary. If I find what is triggering the
toobusy in my system, I will post back here in case others are concerned. In the mean time, since the forum is working like a charm, I have no reason to worry too much.
While I am at it, thanks for your job, you and the whole NodeBB team.
On my dev environment
Isn't this disabled unless it's on production?
Yeah, since the commit you made, it's disabled on dev mode, although I think he means his dev install of NodeBB.