Skip to content

NodeBB 1.19.3

Solved Performance
33 2 16.5k 1
  • Hello 🙂

    I find that since version 1.19.3 of NodeBB, the refresh of the pages is much longer than usual.

    I did a test with the same config on my VM and in 1.19.2, the refresh was much faster.
    idem to connect to ACP.

    Am I the only one who noticed this?

    wrote on last edited by phenomlab
    #2

    @DownPW I’ve not upgraded yet but will do so at some point today.

    EDIT- just upgraded. Not seeing any slowness yet, but will continue to monitor 😕

  • wrote on last edited by
    #3

    Seems to be my VM virtual disk the problem.

    I try to reinstall Nodebb, very odd i have an internal server error

    here is what I do:

    #
    # Installing Node.js
    #
    
    apt install curl
    curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
    sudo apt-get install -y nodejs
    
    #
    # Database: # Installing MongoDB
    #
    
    V5
    curl -sSL https://www.mongodb.org/static/pgp/server-5.0.asc  -o mongoserver.asc
    gpg --no-default-keyring --keyring ./mongo_key_temp.gpg --import ./mongoserver.asc
    gpg --no-default-keyring --keyring ./mongo_key_temp.gpg --export > ./mongoserver_key.gpg
    sudo mv mongoserver_key.gpg /etc/apt/trusted.gpg.d/
    
    wget -qO - https://www.mongodb.org/static/pgp/server-5.0.asc | sudo apt-key add -
    
    echo "deb http://repo.mongodb.org/apt/debian buster/mongodb-org/5.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-5.0.list
    
    sudo apt update
    sudo apt-get install -y mongodb-org
    
    sudo systemctl start mongod
    sudo systemctl status mongod
    
    mongo
    use admin
    > db.createUser( { user: "admin", pwd: "nodebb", roles: [ { role: "root", db: "admin" } ] } )
    
    use nodebb
    > db.createUser( { user: "nodebb", pwd: "nodebb", roles: [ { role: "readWrite", db: "nodebb" }, { role: "clusterMonitor", db: "admin" } ] } )
    
    quit()
    
    sudo nano /etc/mongod.conf
    	security:
    		authorization: enabled
    
    sudo systemctl restart mongod
    
    
    #
    # Installing NodeBB
    #
    
    sudo apt install -y git
    
    cd /home/nodebb
    git clone -b v1.18.x https://github.com/NodeBB/NodeBB.git nodebb
    cd nodebb
    
    ./nodebb setup
    ./nodebb start
    

    very odd

  • Seems to be my VM virtual disk the problem.

    I try to reinstall Nodebb, very odd i have an internal server error

    here is what I do:

    #
    # Installing Node.js
    #
    
    apt install curl
    curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
    sudo apt-get install -y nodejs
    
    #
    # Database: # Installing MongoDB
    #
    
    V5
    curl -sSL https://www.mongodb.org/static/pgp/server-5.0.asc  -o mongoserver.asc
    gpg --no-default-keyring --keyring ./mongo_key_temp.gpg --import ./mongoserver.asc
    gpg --no-default-keyring --keyring ./mongo_key_temp.gpg --export > ./mongoserver_key.gpg
    sudo mv mongoserver_key.gpg /etc/apt/trusted.gpg.d/
    
    wget -qO - https://www.mongodb.org/static/pgp/server-5.0.asc | sudo apt-key add -
    
    echo "deb http://repo.mongodb.org/apt/debian buster/mongodb-org/5.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-5.0.list
    
    sudo apt update
    sudo apt-get install -y mongodb-org
    
    sudo systemctl start mongod
    sudo systemctl status mongod
    
    mongo
    use admin
    > db.createUser( { user: "admin", pwd: "nodebb", roles: [ { role: "root", db: "admin" } ] } )
    
    use nodebb
    > db.createUser( { user: "nodebb", pwd: "nodebb", roles: [ { role: "readWrite", db: "nodebb" }, { role: "clusterMonitor", db: "admin" } ] } )
    
    quit()
    
    sudo nano /etc/mongod.conf
    	security:
    		authorization: enabled
    
    sudo systemctl restart mongod
    
    
    #
    # Installing NodeBB
    #
    
    sudo apt install -y git
    
    cd /home/nodebb
    git clone -b v1.18.x https://github.com/NodeBB/NodeBB.git nodebb
    cd nodebb
    
    ./nodebb setup
    ./nodebb start
    

    very odd

    wrote on last edited by
    #4

    @DownPW And did that work ?

  • wrote on last edited by
    #5

    nope, i have test the installation for 2 times

    this error when access:

    internal server error

    very odd, I’ve never had any problems when installing nodebb

  • nope, i have test the installation for 2 times

    this error when access:

    internal server error

    very odd, I’ve never had any problems when installing nodebb

    wrote on last edited by phenomlab
    #6

    @DownPW If you issue ./nodebb start does this work if you then issue ./nodebb log ? Sounds like a NGINX issue to me

  • wrote on last edited by
    #7

    No nginx conf

    ./nodebb sytart = no error

    ./nodebb log when i access

    2022-02-17T15:26:25.097Z [4567/1884] - error: /
    Error: Login sessions require session support. Did you forget to use `express-session` middleware?
        at SessionStrategy.authenticate (/home/nodebb/nodebb/node_modules/passport/lib/strategies/session.js:46:41)
        at attempt (/home/nodebb/nodebb/node_modules/passport/lib/middleware/authenticate.js:369:16)
        at authenticate (/home/nodebb/nodebb/node_modules/passport/lib/middleware/authenticate.js:370:7)
        at Layer.handle [as handle_request] (/home/nodebb/nodebb/node_modules/express/lib/router/layer.js:95:5)
        at trim_prefix (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:323:13)
        at /home/nodebb/nodebb/node_modules/express/lib/router/index.js:284:7
        at Function.process_params (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:341:12)
        at next (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:275:10)
        at initialize (/home/nodebb/nodebb/node_modules/passport/lib/middleware/initialize.js:89:5)
        at Layer.handle [as handle_request] (/home/nodebb/nodebb/node_modules/express/lib/router/layer.js:95:5)
    TypeError: Cannot read property 'startsWith' of undefined
        at Object.getBaseUrl (/home/nodebb/nodebb/node_modules/nodebb-plugin-emoji/build/lib/base-url.js:7:25)
        at Object.addStylesheet [as method] (/home/nodebb/nodebb/node_modules/nodebb-plugin-emoji/build/lib/index.js:75:32)
        at fireMethod (/home/nodebb/nodebb/src/plugins/hooks.js:137:25)
        at Object.fireFilterHook [as filter] (/home/nodebb/nodebb/src/plugins/hooks.js:168:18)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async Hooks.fire (/home/nodebb/nodebb/src/plugins/hooks.js:105:17)
        at async Promise.all (index 1)
        at async Tags.parse (/home/nodebb/nodebb/src/meta/tags.js:146:18)
        at async renderMethod (/home/nodebb/nodebb/src/middleware/render.js:49:12)
        at async ServerResponse.renderOverride [as render] (/home/nodebb/nodebb/src/middleware/render.js:92:5)
    
  • No nginx conf

    ./nodebb sytart = no error

    ./nodebb log when i access

    2022-02-17T15:26:25.097Z [4567/1884] - error: /
    Error: Login sessions require session support. Did you forget to use `express-session` middleware?
        at SessionStrategy.authenticate (/home/nodebb/nodebb/node_modules/passport/lib/strategies/session.js:46:41)
        at attempt (/home/nodebb/nodebb/node_modules/passport/lib/middleware/authenticate.js:369:16)
        at authenticate (/home/nodebb/nodebb/node_modules/passport/lib/middleware/authenticate.js:370:7)
        at Layer.handle [as handle_request] (/home/nodebb/nodebb/node_modules/express/lib/router/layer.js:95:5)
        at trim_prefix (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:323:13)
        at /home/nodebb/nodebb/node_modules/express/lib/router/index.js:284:7
        at Function.process_params (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:341:12)
        at next (/home/nodebb/nodebb/node_modules/express/lib/router/index.js:275:10)
        at initialize (/home/nodebb/nodebb/node_modules/passport/lib/middleware/initialize.js:89:5)
        at Layer.handle [as handle_request] (/home/nodebb/nodebb/node_modules/express/lib/router/layer.js:95:5)
    TypeError: Cannot read property 'startsWith' of undefined
        at Object.getBaseUrl (/home/nodebb/nodebb/node_modules/nodebb-plugin-emoji/build/lib/base-url.js:7:25)
        at Object.addStylesheet [as method] (/home/nodebb/nodebb/node_modules/nodebb-plugin-emoji/build/lib/index.js:75:32)
        at fireMethod (/home/nodebb/nodebb/src/plugins/hooks.js:137:25)
        at Object.fireFilterHook [as filter] (/home/nodebb/nodebb/src/plugins/hooks.js:168:18)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async Hooks.fire (/home/nodebb/nodebb/src/plugins/hooks.js:105:17)
        at async Promise.all (index 1)
        at async Tags.parse (/home/nodebb/nodebb/src/meta/tags.js:146:18)
        at async renderMethod (/home/nodebb/nodebb/src/middleware/render.js:49:12)
        at async ServerResponse.renderOverride [as render] (/home/nodebb/nodebb/src/middleware/render.js:92:5)
    
    wrote on last edited by phenomlab
    #8

    @DownPW Potentially dumb question, but why is the path /home/nodebb/nodebb ?

    Also, why are you trying to install the 18.x branch when you should be using 19.x ?

    I see

    cd /home/nodebb
    git clone -b v1.18.x https://github.com/NodeBB/NodeBB.git nodebb
    cd nodebb
    

    This should be

    cd /home/nodebb
    git clone -b v1.19.x https://github.com/NodeBB/NodeBB.git nodebb
    cd nodebb
    
  • 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


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
  • External Links - New Window

    Solved Customisation nodebb links settings
    8
    2 Votes
    8 Posts
    2k Views
    phenomlab
    @Sampo2910 search the forum here for ogproxy which is the client side version of that plugin I wrote. It’s in use here on this forum.
  • 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 socket with CloudFlare

    Solved Performance socket cloudflare nodebb
    24
    3 Votes
    24 Posts
    14k Views
    DownPW
    Solved. Tuto here and here
  • SEO and Nodebb

    Performance nodebb seo
    2
    2 Votes
    2 Posts
    2k Views
    phenomlab
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • 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):
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • ineffecient use of space on mobile

    Solved Customisation nodebb
    10
    2
    7 Votes
    10 Posts
    4k Views
    crazycells
    @phenomlab Thanks
  • NodeBB Footer

    Solved Customisation footer nodebb
    10
    1 Votes
    10 Posts
    4k Views
    JAC
    @phenomlab said in NodeBB Footer: @jac and you. Hope all is well and you recover quickly Thanks pal