Skip to content

nodebb loading emojis

Solved Configure
16 2 5.7k 1
  • wrote on last edited by
    #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 😉

  • wrote on last edited by DownPW
    #13

    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 😉

    wrote on last edited by
    #2

    @DownPW are you using any page rules in Cloudflare?

  • wrote on last edited by DownPW
    #3

    @phenomlab

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

    image.png

  • wrote on last edited by
    #4

    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

    wrote on last edited by
    #5

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

  • wrote on last edited by
    #6

    @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

    wrote on last edited by
    #7

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

    wrote on last edited by
    #8

    @DownPW Same issue

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

  • wrote on last edited by DownPW
    #9

    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; 
    
    wrote on last edited by
    #10

    @DownPW 100% still there in incognito view

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

  • wrote on last edited by
    #11

    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

    wrote on last edited by
    #12

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

  • wrote on last edited by DownPW
    #13

    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.

    wrote on last edited by
    #14

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

    wrote on last edited by
    #15

    @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

    wrote on last edited by
    #16

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

  • DownPW 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
  • Getting Eror When Started NodeBB

    Solved Configure bug
    7
    1
    2 Votes
    7 Posts
    2k Views
    cagatay
    @phenomlab yes i did. i deleted one of plugin then it started to work normally.
  • Fixed background to nodebb forum

    Solved Configure nodebb
    25
    4 Votes
    25 Posts
    10k Views
    phenomlab
    @Panda said in Fixed background to nodebb forum: Chatgpt told me the ::before method. Go figure
  • Composer Zen icon?

    Solved Configure nodebb
    8
    1
    2 Votes
    8 Posts
    3k Views
    phenomlab
    @DownPW exactly. Not really a new concept, and in all honesty, not something I’ve ever used. If you consider the need to add links and references, or citations, you’d need to be able to see other parts of the screen!
  • NodeBB: updating Admin details not working

    Solved Configure nodebb admin
    17
    3 Votes
    17 Posts
    5k Views
    phenomlab
    @mventures Ok. No issues
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    3k Views
    phenomlab
    @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: 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 3.0 alpha1 : Error on install

    Solved Configure nodebb version 3 install error
    19
    2 Votes
    19 Posts
    7k Views
    DownPW
    @phenomlab Work now
  • [NODEBB] Welcome Message

    Solved Customisation css html nodebb
    20
    2
    13 Votes
    20 Posts
    9k Views
    phenomlab
    @DownPW the ‘js’ code for the banner takes the time from the client, so what it displays really depends on the regional settings for the operating system. I’ve not seen this issue myself but would like to see some examples of screenshots if possible.
  • NodeBB metadata

    Solved Configure nodebb
    4
    2 Votes
    4 Posts
    2k Views
    JAC
    @phenomlab said in NodeBB metadata: @jac Are you sure ? https://www.google.co.uk/search?q=site%3Astockportcounty.fans&sxsrf=AOaemvLwnaZL-PliU_2dBOg_Eo1pMVhBjg%3A1638982328139&source=hp&ei=uOKwYeatBcOsad3yp7AE&iflsig=ALs-wAMAAAAAYbDwyLBSDcG5XYoFCKwQFhgz94wTxOcV&ved=0ahUKEwjm6dX71NT0AhVDVhoKHV35CUYQ4dUDCAk&uact=5&oq=site%3Astockportcounty.fans&gs_lcp=Cgdnd3Mtd2l6EAM6BAgjECc6CwgAEIAEELEDEIMBOg4ILhCABBCxAxDHARCjAjoRCC4QgAQQsQMQgwEQxwEQowI6BQguEIAEOggIABCABBCxAzoFCAAQgAQ6CAguELEDEIMBOgsILhCABBDHARCvAToICC4QgAQQsQM6BQgAELEDOgsILhCABBDHARDRAzoLCAAQgAQQsQMQyQM6BQgAEJIDUABYySZg0CdoAHAAeACAAW2IAa0NkgEEMjMuMpgBAKABAQ&sclient=gws-wiz Fair enough 🤪🤪.