Skip to content

NodeBB 1.19.3

Solved Performance
33 2 16.5k 1
  • @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

  • @phenomlab

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

    wrote on last edited by
    #29

    @DownPW agreed. What happens actually if you change the loading order of that plugin ? You can do that from the ACP -> Plugins

  • wrote on last edited by
    #30

    I put emoji plugin on first load and this :

    7a964714-be9a-4617-9092-225c039e0a9b-image.png

  • I put emoji plugin on first load and this :

    7a964714-be9a-4617-9092-225c039e0a9b-image.png

    wrote on last edited by
    #31

    @DownPW makes no difference then.

  • wrote on last edited by DownPW
    #32

    yes

    dfb0fe53-2897-4660-9390-ab75eee678bd-image.png

    The path doesn’t exist (Assets/plugins/…)

    e2ff90ba-6379-4c9d-bb52-167f0df89166-image.png

    EDIT:

    Sorry Existing path:
    http://192.168.1.53:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u

    e4fd5733-8993-4dbb-8115-d87e8c5bc50e-image.png

  • wrote on last edited by DownPW
    #33

    @phenomlab

    I find the problem Mark 😉

    The error message indicated this path :

    http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u

    I change the path url on config.json

    47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png

    And all it’s good 🙂

    Weird, I didn’t have to change that path before 1.19.3

    But this does not prevent the problem from a clean install with Emoji Plugin


    EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup

    For resume: NodeJS 16_x with 1.18.x is ok

  • 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.
  • Custom html in nodebb to prevent cache

    Unsolved Configure nodebb
    18
    2 Votes
    18 Posts
    5k Views
    phenomlab
    @Panda You’ll need to do that with js. With some quick CSS changes, it looks like this [image: d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png] The colour choice is still really hard on the eye, but at least you can now read the text
  • NodeBB socket with CloudFlare

    Solved Performance socket cloudflare nodebb
    24
    3 Votes
    24 Posts
    14k Views
    DownPW
    Solved. Tuto here and here
  • www. Infront stops website access?

    Solved Configure nodebb
    10
    1 Votes
    10 Posts
    3k Views
    phenomlab
    @Panda because there is no match for the DNS entry specified. The receiving web server parses the headers looking for a destination hostname to match, and anything the web server is unable to resolve will be sent back to the root.
  • Following the API docs but its not clear ...

    Solved Customisation api nodebb
    8
    2 Votes
    8 Posts
    3k Views
    phenomlab
    @Panda you’d be surprised. If you consider that you’d need to use the API to be able to populate a WordPress widget for example (which in turn would of course be PHP), taking this route is still immensely popular.
  • NodeBB inline videoplayer

    Solved Customisation nodebb
    12
    3 Votes
    12 Posts
    5k Views
    Panda
    @phenomlab YAY! It works Thanks so much
  • Bootstrap Version

    Solved Customisation nodebb bootstrap
    8
    5 Votes
    8 Posts
    3k Views
    Madchatthew
    @phenomlab That will be nice once they have completed that. It will be interesting to see how long that takes. So for now I will use custom css to make it look the way I want. Frameworks just make things a little faster. Thanks @phenomlab
  • NodeBB slow after DB recovery

    Solved Performance performance nodebb
    1
    5 Votes
    1 Posts
    967 Views
    No one has replied