Skip to content

nodebb loading emojis

Solved Configure
16 2 4.2k 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
  • Removing blue 'moved' tag from post

    Solved Configure nodebb
    16
    2
    3 Votes
    16 Posts
    4k Views
    @phenomlab Ah, got it working! I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters. So made the new fork title longer and button responded.
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    2k Views
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • NodeBB: Opening the Composer for replies

    Solved Configure cms composer
    2
    0 Votes
    2 Posts
    888 Views
    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below [image: 1681314389744-82ca1209-31be-4a51-a641-9887b5a238b8-image.png] Failing that, you’ll need to use the reply button in the sticky toolbar [image: 1681314442570-1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png]
  • NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    5k Views
    @DownPW I still do not see any issues.
  • NodeBB: Creating the Swatch modes

    Solved Configure swatch
    2
    0 Votes
    2 Posts
    873 Views
    @mventures the swatch feature you refer to isn’t a NodeBB plugin, but a utility that I wrote that handles this. It is available for v2 (as you can see here) but I’ve stopped developing and releasing the code because it has been entirely rewritten to work for v3. If you’d like the code, this is possible, but you’ll need to upgrade to v3 first.
  • Podcast Share NodeBB

    Solved Configure podcast nodebb
    15
    4 Votes
    15 Posts
    4k Views
    @cagatay You could experiment with nodebb-plugin-ns-embed but I expect the x-origin tag on the remote site to prevent playback.
  • Changing Background on NodeBB

    Solved Customisation background image nodebb
    4
    0 Votes
    4 Posts
    2k Views
    @cagatay You’d target the body tag and use the below line of CSS background: url(/assets/customcss/backgrounds/default/default.png) no-repeat center center fixed; Obviously, you need to change the path to suit where your image is being stored. More info around the background property can be found here https://www.w3schools.com/cssref/css3_pr_background.php
  • Blinking text Effect

    Customisation nodebb text effect css
    3
    5 Votes
    3 Posts
    1k Views
    @phenomlab I love it too @phenomlab said in Blinking text Effect: Has that “broken neon light” look that you see in films. It’s exactly that, kind of old neon signs of bar or pubs a bit cyberpunk too