Skip to content

NodeBB 1.19.3

Solved Performance
33 2 16.5k 1
  • wrote on last edited by
    #9

    I have test to install 1.19.x too and i have error too

  • I have test to install 1.19.x too and i have error too

    wrote on last edited by
    #10

    @DownPW and you are executing ./nodebb setup from the correct directory ?

  • @DownPW and you are executing ./nodebb setup from the correct directory ?

    wrote on last edited by
    #11
  • wrote on last edited by
    #12

    I think they really have a problem on the github and coincidentally it’s a plugin on which they had big problems that was in question. (emoji)

  • I think they really have a problem on the github and coincidentally it’s a plugin on which they had big problems that was in question. (emoji)

    wrote on last edited by
    #13

    @DownPW Looking at the error message, I’d say you’re right.

  • wrote on last edited by DownPW
    #14

    @phenomlab

    here a gif for the problem of perf.
    On a clean install of nodeBB on a clean install server VM

    The problem is just when I refresh the page entierly or ACP access

    alt text

    No problem on 1.18.x or 1.19.2

    very odd

  • @phenomlab

    here a gif for the problem of perf.
    On a clean install of nodeBB on a clean install server VM

    The problem is just when I refresh the page entierly or ACP access

    alt text

    No problem on 1.18.x or 1.19.2

    very odd

    wrote on last edited by
    #15

    @DownPW Looks like that’s waiting for a response from something. Have you run this site through the F12 developer tools -> Network tab to see where the delay is ?

  • wrote on last edited by DownPW
    #16

    @phenomlab

    Thanks for the tip

    chance 😉

    335905d5-03e1-4f81-83a6-93e5f30d9bfa-image.png

  • @phenomlab

    Thanks for the tip

    chance 😉

    335905d5-03e1-4f81-83a6-93e5f30d9bfa-image.png

    wrote on last edited by
    #17

    @DownPW 8ms is nothing - less than one second… ?

  • wrote on last edited by DownPW
    #18

    @phenomlab

    you not see at the good place 🙂
    EDIT:

    dcba37d8-db4f-4b8d-93a9-ac883171bebc-image.png

    coincidence? Emoji CSS failed !
    I don’t believe

    I think we put the finger on something

  • @phenomlab

    you not see at the good place 🙂
    EDIT:

    dcba37d8-db4f-4b8d-93a9-ac883171bebc-image.png

    coincidence? Emoji CSS failed !
    I don’t believe

    I think we put the finger on something

    wrote on last edited by
    #19

    @DownPW Yes, you’re right. For some strange reason, that CSS file is not being served - but should be on your server if you check the path.

  • wrote on last edited by DownPW
    #20

    yes it still here

    EDIT:

    I have remove the directory when I have the problem of install with 1.18.x

    But when I upgrade to 1.19.3, he have reinstalled by default

  • yes it still here

    EDIT:

    I have remove the directory when I have the problem of install with 1.18.x

    But when I upgrade to 1.19.3, he have reinstalled by default

    wrote on last edited by
    #21

    @DownPW I see this

    a325f036-d5d1-44b8-b583-fd6a913a1b43-image.png

  • @DownPW I see this

    a325f036-d5d1-44b8-b583-fd6a913a1b43-image.png

    wrote on last edited by
    #22

    @phenomlab on your website ?

  • @phenomlab on your website ?

    wrote on last edited by
    #23

    @DownPW No - on yours.

  • wrote on last edited by
    #24

    ha lol ok

  • wrote on last edited by DownPW
    #25

    @phenomlab

    because you are guest maybe because not me

  • wrote on last edited by
    #26

    test admin:nodebb

  • test admin:nodebb

    wrote on last edited by
    #27

    @DownPW Same error when logged in

    a42f594b-29be-4ddc-b52f-587f2c8948c9-image.png

  • @DownPW Same error when logged in

    a42f594b-29be-4ddc-b52f-587f2c8948c9-image.png

    wrote on last edited by DownPW
    #28

    @phenomlab

    yes I think there is a problem with that plugin.
    Maybe open a topic with this on nodeBB communauty


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
  • 4 Votes
    3 Posts
    2k Views
    crazycells
    thanks @DownPW ! this is definitely very helpful.
  • 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.
  • NodeBB v3.0.0-rc.1

    Performance nodebb v3.0.0
    1
    1 Votes
    1 Posts
    701 Views
    No one has replied
  • Optimum config for NodeBB under NGINX

    Performance nginx performance
    4
    3 Votes
    4 Posts
    2k Views
    phenomlab
    @crazycells hi - no security reason, or anything specific in this case. However, the nginx.conf I posted was from my Dev environment which uses this port as a way of not interfering with production. And yes, I use clustering on this site with three instances.
  • 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
  • Changing Background on NodeBB

    Solved Customisation background image nodebb
    4
    0 Votes
    4 Posts
    2k Views
    phenomlab
    @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
  • NodeBB slow after DB recovery

    Solved Performance performance nodebb
    1
    5 Votes
    1 Posts
    967 Views
    No one has replied
  • creating topic specific widgets

    Solved Customisation nodebb
    16
    10 Votes
    16 Posts
    7k Views
    phenomlab
    @crazycells said in creating topic specific widgets: Additionally if hide class exists, why are we re-defining it? We’re not 🤭 I misspelled it - it should be hidden