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
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Plugin to show images in teasers

    General nodebb teaser image plugin hook
    6
    1
    2 Votes
    6 Posts
    2k Views
    phenomlab
    @dave1904 I’d start by adding a console.log function to hookData so you can see what is being returned return hookData; console.log(hookData):
  • NodeBB: Favicon upload issue

    Solved Configure nodebb favicon
    12
    1
    3 Votes
    12 Posts
    4k Views
    mventures
    @phenomlab I am on a Mac, so I used the “Option + Command + I”, and then performed the steps. It loaded my favicon! I checked on Firefox which I haven’t used before, and it showed my favicon also! That’s fantastic and thank you for the help!
  • NodeBB: Creating pages

    Solved Configure nodebb create page
    9
    0 Votes
    9 Posts
    4k Views
    mventures
    OK, I think I have figured out how to place a link in the footer which will click to a new page.
  • restarting nodebb on boot

    Unsolved Configure nodebb
    3
    1 Votes
    3 Posts
    2k Views
    phenomlab
    @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.
  • Top Ranked Forums

    Chitchat nodebb top ranked
    9
    1
    3 Votes
    9 Posts
    3k Views
    phenomlab
    The real issue here is that most people consider forums to be “dead” in the sense that nobody uses them anymore, and social media groups have taken their place. Their once dominant stance in the 90’s and early 00’s will never be experienced again, but having said that, there are a number of forums that did in fact survive the social media onslaught, and still enjoy a large user base. Forums tend to be niche. One that immediately sticks out is Reddit - despite looking like it was designed in the 80s, it still has an enormous user base. Another is Stack Overflow, which needs no introduction. The key to any forum is the content it offers, and the more people whom contribute in terms of posting , the more popular and widely respected it becomes as a reliable source of information. Forums are still intensely popular with gamers, alongside those that offer tips on hacking etc.
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    5k Views
    phenomlab
    @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.
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    17k Views
    phenomlab
    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.