Skip to content

Upgrade Problem from 2.8.3 to 2.8.4

Solved Configure
35 3 11.6k 1
  • @phenomlab permission for user right? so i did not change any permison for nodebb user so why it caused or what i should do for to give permision to nodebb user? till 2.8.2 nodebb user can upgrade any permission case what happened with 2.8.4 🙂

    wrote on last edited by
    #9

    @cagatay are you able to remove that plugin and reinstall or does it present the same error?

  • @cagatay are you able to remove that plugin and reinstall or does it present the same error?

    wrote on last edited by
    #10

    @phenomlab yeap i removed the plugin and reinstall it problem is fixed.

  • phenomlab phenomlab has marked this topic as solved on
  • @cagatay are you able to remove that plugin and reinstall or does it present the same error?

    wrote on last edited by
    #11

    @phenomlab i deleted emoji plugin but while upgraded to 2.8.6 faced same problem.
    cant understand whats going on.

  • @phenomlab i deleted emoji plugin but while upgraded to 2.8.6 faced same problem.
    cant understand whats going on.

    wrote on last edited by
    #12

    @cagatay can you provide the logs?

  • @cagatay can you provide the logs?

    wrote on last edited by
    #13

    @phenomlab from now like this;

    71faca9a-4e66-4c73-b521-084272c6ab0a-image.png

    but when upgrading;

    97aa618c-efd9-4edd-be72-a294d35a303d-image.png

  • @phenomlab from now like this;

    71faca9a-4e66-4c73-b521-084272c6ab0a-image.png

    but when upgrading;

    97aa618c-efd9-4edd-be72-a294d35a303d-image.png

    wrote on last edited by
    #14

    @cagatay does it work if you remove this plugin, perform the upgrade, and then put it back afterwards?

  • @cagatay does it work if you remove this plugin, perform the upgrade, and then put it back afterwards?

    wrote on last edited by
    #15

    @phenomlab i removed the plugin then upgraded but faced same eror…

  • @phenomlab i removed the plugin then upgraded but faced same eror…

    wrote on last edited by DownPW
    #16

    @cagatay @phenomlab

    Maybe reset permissions on all nodebb directory like this ?

    chown -R yournodebbuser:yournodebbuser /home/youruser/yournodebbdirectory
    
    chown -R nodes:nodes /home/nodes/nodebb
    

    because I see permissions error on /home/nodes/nodebb/builds/.... in the last screenshot

    And .upgrade and or rebuild nodebb

    ??

  • @cagatay @phenomlab

    Maybe reset permissions on all nodebb directory like this ?

    chown -R yournodebbuser:yournodebbuser /home/youruser/yournodebbdirectory
    
    chown -R nodes:nodes /home/nodes/nodebb
    

    because I see permissions error on /home/nodes/nodebb/builds/.... in the last screenshot

    And .upgrade and or rebuild nodebb

    ??

    wrote on last edited by
    #17

    @DownPW yes, but we really need to understand why and how these permissions are changing.

  • @DownPW yes, but we really need to understand why and how these permissions are changing.

    wrote on last edited by phenomlab
    #18

    @DownPW @cagatay I found the reason why. This plugin is in fact faulty. I installed it myself because I wanted to add that feature to Sudonix. Not only does it push socket.io through the roof (and adds at least 2 seconds lag to each transaction)

    https://community.nodebb.org/topic/10225/nodebb-plugin-reactions-reactions-plugin-for-nodebb/60?_=1675778336803

    It also is impossible to remove by using the GUI - see my experience below, which is exactly the same as @cagatay

    5b8bb524-bc24-4376-8f57-9c5656c1d96c-image.png

    Not great. The only way to remove this cleanly is from the CLI

    npm remove @nodebb/nodebb-plugin-reactions
    ./nodebb build
    ./nodebb restart
    

    I remember flagging this a while back - it’s here

    https://github.com/NodeBB/NodeBB/issues/10582

    And here (one I raised)

    https://github.com/NodeBB-Community/nodebb-plugin-reactions/issues/8

    So, my advice is NOT to use this plugin currently as the unnecessary load it places on your forum isn’t worth the functionality it provides.

  • @DownPW @cagatay I found the reason why. This plugin is in fact faulty. I installed it myself because I wanted to add that feature to Sudonix. Not only does it push socket.io through the roof (and adds at least 2 seconds lag to each transaction)

    https://community.nodebb.org/topic/10225/nodebb-plugin-reactions-reactions-plugin-for-nodebb/60?_=1675778336803

    It also is impossible to remove by using the GUI - see my experience below, which is exactly the same as @cagatay

    5b8bb524-bc24-4376-8f57-9c5656c1d96c-image.png

    Not great. The only way to remove this cleanly is from the CLI

    npm remove @nodebb/nodebb-plugin-reactions
    ./nodebb build
    ./nodebb restart
    

    I remember flagging this a while back - it’s here

    https://github.com/NodeBB/NodeBB/issues/10582

    And here (one I raised)

    https://github.com/NodeBB-Community/nodebb-plugin-reactions/issues/8

    So, my advice is NOT to use this plugin currently as the unnecessary load it places on your forum isn’t worth the functionality it provides.

    wrote on last edited by
    #19

    @phenomlab i dont have this plugin Mark. So the problem is currently continue.

  • @phenomlab i dont have this plugin Mark. So the problem is currently continue.

    wrote on last edited by
    #20

    @cagatay Sorry - my mistake.

  • @cagatay Sorry - my mistake.

    wrote on last edited by
    #21

    @phenomlab not fixed yet.

  • @phenomlab not fixed yet.

    wrote on last edited by
    #22

    @cagatay are you installing this plugin as root, or as the user running NodeBB?

  • @cagatay are you installing this plugin as root, or as the user running NodeBB?

    wrote on last edited by cagatay
    #23

    @phenomlab as user.
    as a root i dont want to use for Nodebb.
    on the other hand the forum is working normally. it is happening just when i m upgrading.

  • @phenomlab as user.
    as a root i dont want to use for Nodebb.
    on the other hand the forum is working normally. it is happening just when i m upgrading.

    wrote on last edited by
    #24

    @cagatay I’m not able to replicate this issue within my test environment. What permissions are set for the file and folders on this specific plugin?

  • @cagatay I’m not able to replicate this issue within my test environment. What permissions are set for the file and folders on this specific plugin?

    wrote on last edited by
    #25

    @phenomlab its not problem as for the this moment. lets forget about it.
    we should focus on v3 🙂

  • @phenomlab its not problem as for the this moment. lets forget about it.
    we should focus on v3 🙂

    wrote on last edited by
    #26

    @cagatay I can work with that 😃

  • wrote on last edited by
    #27

    You are getting that message because you have the three plugins below installed which all depend on nodebb-plugin-emoji so you cannot remove the main plugin without first removing those

    1679316592601-a88285fb-6417-419a-9f27-731cae619e78-image.png

    I’ve done it for you anyway 🙂

    image.png

    You should be able to upgrade now.

  • phenomlab phenomlab has marked this topic as solved on
  • wrote on last edited by
    #28

    Users can not use emoji from now 😞 how i can fix it?


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.
  • MogoDB v6 to v7 upgrade

    Solved Configure nodebb
    5
    1 Votes
    5 Posts
    2k Views
    phenomlab
    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.
  • CSS code customization for the link preview plugin

    Solved Customisation css nodebb
    6
    2
    3 Votes
    6 Posts
    3k Views
    phenomlab
    @kadir-ay-0 marking as resolved based on https://community.nodebb.org/topic/17109/manual-build-a-night-mode-for-harmony/5 Please do not raise requests in two places - here and the NodeBB forums. All this does is create unnecessary load for both parties.
  • mongodb backup problem

    Moved Configure mongodb
    3
    1
    1 Votes
    3 Posts
    1k Views
    phenomlab
    You might want to also review this post https://sudonix.org/topic/389/mongodb-backup-script
  • Upgrade issues

    Solved Configure nodebb
    2
    1
    2 Votes
    2 Posts
    1k Views
    DownPW
    Use this code git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x And you will have the latest version without specifying it https://docs.nodebb.org/configuring/upgrade/
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    3k Views
    phenomlab
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • Custom badges

    Solved Customisation nodebb
    103
    2
    49 Votes
    103 Posts
    60k Views
    DownPW
    Perfect
  • Error install plugin

    Solved Customisation plugin nodebb
    8
    1
    1 Votes
    8 Posts
    6k Views
    DownPW
    @pobojmoks Not WP plugin but nodeBB but it a known bug