Skip to content

nodebb loading emojis

Solved Configure
16 2 4.4k 1
  • Hello

    We have a lot of custom émojis on nodebb.

    Sometines we have emojis not loading properly, sometimes they lload corretly after refresh

    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 ?

    35d5bbd5-1219-4db0-b6d9-1a50d5cf8fa8-image.png

    Thanks to communauty 😉

  • 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.

  • Hello

    We have a lot of custom émojis on nodebb.

    Sometines we have emojis not loading properly, sometimes they lload corretly after refresh

    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 ?

    35d5bbd5-1219-4db0-b6d9-1a50d5cf8fa8-image.png

    Thanks to communauty 😉

    @DownPW are you using any page rules in Cloudflare?

  • @phenomlab

    yep you have configured i guess but I don’t see what it’s really for

    image.png

  • I have test to deactivate page rules but idem.

    If you find a solution, I promess you to buy you cofee my friends lol

  • I have test to deactivate page rules but idem.

    If you find a solution, I promess you to buy you cofee my friends lol

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

  • @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

    image.png

  • @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

    image.png

    @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

    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 ?

    @DownPW Same issue

    b013fb18-b61a-4deb-bee9-0af3d79900c8-image.png

  • 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; 
    
  • 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; 
    

    @DownPW 100% still there in incognito view

    98d827c5-13be-41c7-ad77-59ffc54e9ce5-image.png

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

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

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

  • 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.

  • 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.

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

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

    @phenomlab

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

  • @phenomlab

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

    @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.

  • DownPWundefined DownPW has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Whitespace fixes in Nodebb

    Solved Customisation nodebb
    18
    2
    7 Votes
    18 Posts
    5k Views
    @Panda Just circling back here with something of an update (which I think you’ll like). I’ve completely restructured the ranking system. There are now less ranks, with a higher point threshold to reach them. More importantly, if you reload the site, you’ll notice that the ranks are now icons. I also removed the “Author” badge, and made this a single icon, which (to me) looks much better.
  • NodeBB: hCaptcha

    Solved Configure hcaptcha
    15
    2 Votes
    15 Posts
    3k Views
    @mventures none that I know of. I don’t recall selecting these either for mine.
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    2k Views
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: 1680448167972-fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • NodeBB: The global Search option

    Solved Configure search nodebb
    5
    0 Votes
    5 Posts
    1k Views
    @mventures Yes, exactly. The other icon will restart NodeBB whilst the first icon I referenced will rebuild (recompile) it. The huge strength of NodeBB over Flarum (for example) is that the code is precompiled, and called once at boot. PHP’s code has to repeatedly reload code from source making it much slower.
  • restarting nodebb on boot

    Unsolved Configure nodebb
    3
    1 Votes
    3 Posts
    2k Views
    @eeeee said in restarting nodebb on boot: can I just run nodebb under nodemon for auto restarts? It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.
  • what does sound/mute button do?

    Solved Customisation nodebb
    20
    1
    9 Votes
    20 Posts
    5k Views
    @crazycells Yeah, looking at the plugin itself, that’s a hard coded limit [image: 1653494282106-3d6dbc10-185b-4102-9470-0c2731a10750-image.png] I’ll probably remove that… eventually…
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    4k Views
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • NodeBB - Created pages not found?

    General
    20
    3 Votes
    20 Posts
    5k Views
    @jac Exactly. Hard point to argue.