NODEBB: Nginx error performance & High CPU

[DownPW]

@phenomlab

Ok I will see it for better worker_processes value

I add a rate limite request and limit_conn_zone on http block and vhost block :

– nginx.conf:

http {

	#Requete maximun par ip 
	limit_req_zone $binary_remote_addr zone=flood:10m rate=100r/s; 
	#Connexions maximum par ip 
	limit_conn_zone $binary_remote_addr zone=ddos:1m;

-- vhost.conf :
        location / {
				
				limit_req zone=flood burst=100 nodelay; 
				limit_conn ddos 10;

–> I have test other value for rate and burst but they cause problem access to the forum. If you have better, I take it

I add today a proxy_read_timeout on vhost.conf (60 by default)

proxy_read_timeout 180;

I have deactivate underattack mode on CF and change for high Level

I have add other rules on CF waf :

[phenomlab]

@DownPW what settings do you have in advanced (in settings) for rate limit etc?

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW what settings do you have in advanced (in settings) for rate limit etc?

In cloudflare ?

[DownPW]

@phenomlab

I wanted to test awstats on virtualmin with root account and it hasn’t updated since August 2022.

I wanted to regenerate the files but I have a problem of rights.

What do you think ? and how t ore-generate a rapport correctly

I would like to use it to better manage the @ips that connect to the server

[phenomlab]

@DownPW no, sorry - in NodeBB ACP

[phenomlab]

@DownPW from recollection, awstats is accessible via the web front end, so (for example) https://mydomain.com/awstats

However, as you are pushing everything into a reverse proxy you’ll need to add a custom route in the nginx.conf file you are using on the website so this can be rendered outside of NodeBB.

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW no, sorry - in NodeBB ACP

Here is the value

[phenomlab]

@DownPW what is the result of disabling it altogether? That will resolve the 503 rate limit error but could we leave the system exposed to bring overwhelmed.

[phenomlab]

@DownPW you should also review this

https://docs.nodebb.org/configuring/scaling/

In particular, the part concerning proxied assets.

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW from recollection, awstats is accessible via the web front end, so (for example) https://mydomain.com/awstats

However, as you are pushing everything into a reverse proxy you’ll need to add a custom route in the nginx.conf file you are using on the website so this can be rendered outside of NodeBB.

Thats why I have a permission error like the screen? Odd

Nope, Awstats is accessible like this via Virtualmin:

https://XXXX:8443/virtualmin-awstats/view.cgi?config=XXXXXX.XX

I have jsut an error of permission whe nI test to regenerate a Report because the script can’t access to log file

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW what is the result of disabling it altogether? That will resolve the 503 rate limit error but could we leave the system exposed to bring overwhelmed.

Disabling What ? Traffic management? HSTS ?

[phenomlab]

@DownPW said in NODEBB: Nginx error performance & High CPU:

Thats why I have a permission error like the screen? Odd

No, not at all. That error is because www-data owns the files when it should be the account you are using to run the website itself under.

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW said in NODEBB: Nginx error performance & High CPU:

Thats why I have a permission error like the screen? Odd

No, not at all. That error is because www-data owns the files when it should be the account you are using to run the website itself under.

I thought that was weird

strange than that.

–> Would you have a solution so that I can regenerate the report and use awstats via virtualmin?

[phenomlab]

@DownPW try this
https://manpages.org/awstats

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@DownPW try this
https://manpages.org/awstats

It worked with the following command (very long) in cli but I’m afraid it won’t work with the virtualmin module

awstats -config=XXX-XXX.XXX -update

[phenomlab]

@DownPW yes, that was a command line to get you the immediate information you needed. Did you try adding the necessary config to nginx in order that it bypasses the reverse proxy?

[crazycells]

@DownPW one day a year, we have the same problem in our forum, where several thousand users become online at the same minute and get similar problems… but we are getting better each year at handling this…

I do not have full technical details about our solution but I know for sure that using NodeBB that listens to three ports help… 4567, 4568, and 4569… Is your NodeBB set up this way?

[phenomlab]

@crazycells said in NODEBB: Nginx error performance & High CPU:

4567, 4568, and 4569… Is your NodeBB set up this way?

It’s not (I set their server up). Sudonix is not configured this way either, but from memory, this also requires redis to handle the session data. I may configure this site to do exactly that.

[DownPW]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@crazycells said in NODEBB: Nginx error performance & High CPU:

4567, 4568, and 4569… Is your NodeBB set up this way?

It’s not (I set their server up). Sudonix is not configured this way either, but from memory, this also requires redis to handle the session data. I may configure this site to do exactly that.

yep it’s not but it interests me a lot.
I see the documentation but I would have to adapt to our configuration and is it really worth doing?
Where I put ionode directives? on nginx.conf or vhost your_website.conf ? I think on nginx.conf

And where put proxy_pass directive? on nginx.conf or vhost your_website.Conf ?

It’s still pretty blurry but I just took a look at it;

https://docs.nodebb.org/configuring/scaling/

[phenomlab]

@DownPW It’s more straightforward than it sounds, although can be confusing if you look at it for the first time. I’ve just implemented it here. Can you provide your nginx config and your config.json (remove password obviously)

Thanks