nodebb loading emojis

[phenomlab]

@DownPW I like a challenge . I’ll take a look at this tomorrow.

[phenomlab]

@DownPW you’re getting HTTP error 429, which is a rate limit message - your IP is being restricted in terms of what it has access to from the Emoji source perspective

[DownPW]

@phenomlab

Yep I was foud that on the topic on nodeBB communauty. Error 503 It’s the same. I have add rate limit on nginx when we have ddos attack long Time ago and he seems to be better now. I have play with values

Can you test now ?

[phenomlab]

@DownPW Same issue

[DownPW]

very strange @phenomlab I haven’t got error now on the console . And now ?

here is my nginx.conf :

limit_req_zone $binary_remote_addr zone=flood:20m rate=100r/s; 

# Connexions maximum par ip
limit_conn_zone $binary_remote_addr zone=ddos:1m; 

And my website.conf :

   # ddos - flood
   #
   client_body_timeout 5s; # Fermeture des connexions lentes
       client_header_timeout 5s; #  Fermeture des connexions lentes
       limit_conn ddos 10; 
   limit_req zone=flood burst=20 nodelay; 
   limit_req_status 429; 
   proxy_read_timeout 180; 

[phenomlab]

@DownPW 100% still there in incognito view

[DownPW]

yep I have the same on incognito view but not on normal view. Strange

[phenomlab]

@DownPW Cache issue by the sounds of it. Have you cleared CF cache ?

[DownPW]

I delete them now and same result i nincgnito.
–> I delete all rate config on nginx configuration and it seems to be better now. Can you test now @phenomlab ?

but it bothers me, I would have liked to keep nginx protection against flood/ddos attacks with nodebb

Need to find the right setting.

[phenomlab]

@DownPW Yes, working now. At a guess, I’d say your ratelimit settings in nginx.conf are too restrictive.

[DownPW]

@phenomlab

If you have better values rate limit settings for nginx I take it m’y friend

[phenomlab]

@DownPW sure. Let me have a look at this in more detail. I know nginx plus has extensive support for this, but it’s not impossible to get somewhere near acceptable with the standard version.

You might be better off handling this at the Cloudflare level given that it sits in between the requesting client and your server.