nodebb problem loading emojis on composer

DownPW

Hello

We have a lot of custom emojis on nodebb.

Sometines, we have emojis not loading properly, sometimes they load correctly after on refresh or several

I think about a problem of nginx conf maybe, or cache, or Cloudflare but i’m not sure and I don’t know with what to begin my research

An idea about that ?

nodebb 2.8.9 with redis scaling
nodebb-plugin-emoji 4.0.6
cloudflare
nginx

Thanks in advance

julian

You'll have to take a look at the dev console networking tab to see what the problem is...

You might see a 404 or other error that might help narrow the problem down.

DownPW

Exemple here, after a refresh 3 emojis not loading :

503 error.

Very strange, especially since it's random, it's never the same emojis

julian

Are you using a horizontally scaled instance?

DownPW

hmmm I just use nodebb scaling with redis like the documentation : https://docs.nodebb.org/configuring/scaling/

But we suffered DDOS attack some time ago and I had set rate limit in nginx when it happened with crowdsec and crowdsec on cloudflare
Maybe this is what created 503 errors with CloudFlare

I will pursue this idea further on my side. I think it's a good track and I'll be back tomorrow

Troubleshooting Cloudflare 5XX errors | Cloudflare Support docs

When troubleshooting most 5XX errors, the correct course of action is to first contact your hosting provider or site administrator to troubleshoot and gather data.

Cloudflare Docs (developers.cloudflare.com)

julian

Ah ha, that sounds promising

The emoji plugin does load a lot of separate assets, especially when you open the menu.

phenomlab

From what I see on analysis of @DownPW site, this is a ratelimit - HTTP 429.

DownPW

Yep, same idea here.

@julian said in nodebb problem loading emojis on composer:

The emoji plugin does load a lot of separate assets, especially when you open the menu.

Exactly, when we open the menu, WE have a lot of request and my rate limit block.

–> I delete all rate config on my nginx configuration and it seems to be better now.

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

Need to find the right setting.

If nodeBB staff have idea, I take

PitaJ

@DownPW of you're not already serving static assets with nginx, I'd recommend doing that. You should be able to set a separate rate limit for that while still protecting NodeBB.

It may also be possible to whitelist cloudflare so it can bypass the rate limit.