Skip to content

nodebb loading emojis

Solved Configure
16 2 4.1k 1
  • @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
  • Nodebb to Xenforo

    Solved Configure xenforo nodebb
    3
    0 Votes
    3 Posts
    666 Views
    @cagatay as @downpw stated, there isn’t a native tool that will do this for you. You’d need to either develop your own or ask the nodebb team to assist which will be a paid exercise.
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    3k Views
    @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.
  • 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.
  • How to downgrade plugin version on NodeBB

    Solved Customisation downgrade nodebb
    11
    3 Votes
    11 Posts
    3k Views
    @cagatay no problems
  • background color of the footer area

    Solved Customisation nodebb
    7
    1
    7 Votes
    7 Posts
    2k Views
    @phenomlab thank you very much
  • [NodeBB] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    4k Views
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    12k Views
    @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.
  • [NodeBB] custom Gravatar image not showing

    Solved Customisation
    6
    1 Votes
    6 Posts
    2k Views
    @jac said in [NodeBB] custom Gravatar image not showing: @phenomlab said in [NodeBB] custom Gravatar image not showing: @jac are you using Custom ? Sure am mate Confirmed Fixed