Skip to content

Upgrade Problem from 2.8.3 to 2.8.4

Solved Configure
35 3 11.6k 1
  • wrote on last edited by
    #1

    This is my problem that faced when upgrade from 2.8.3 to 2.8.4.

    e7f8bb6c-82d3-48c5-bf38-070e5149f2f0-image.png

  • 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.

  • This is my problem that faced when upgrade from 2.8.3 to 2.8.4.

    e7f8bb6c-82d3-48c5-bf38-070e5149f2f0-image.png

    wrote on last edited by
    #2

    @cagatay that looks very much like a permissions error. Are you attempting the upgrade as the user running NodeBB ?

  • wrote on last edited by DownPW
    #3

    Seems to be a permission problem.

    test ./nodebb upgrade command with root user. (not good but I have this problem one time ago resolved like this) (Mark will yell at me 🙂 )

    go to normal nodebb user and ./nodebb upgrade again

  • @cagatay that looks very much like a permissions error. Are you attempting the upgrade as the user running NodeBB ?

    wrote on last edited by
    #4

    @phenomlab its very interesting but upgrade is done when i login admin panel and nodebb is working without problem.

    so sould i upgrade again by root?

    PS: i always use user not root but user has sudo command 🙂

  • @phenomlab its very interesting but upgrade is done when i login admin panel and nodebb is working without problem.

    so sould i upgrade again by root?

    PS: i always use user not root but user has sudo command 🙂

    wrote on last edited by
    #5

    @cagatay If the upgrade appears to have worked, then you don’t need to run it again, but I would certainly take a look at the nodebb-plugin-emoji issue in more detail as this is 100% a permissions issue

    4d5466ed-cbe5-4752-b90c-0b239e40b3e8-image.png

  • @cagatay If the upgrade appears to have worked, then you don’t need to run it again, but I would certainly take a look at the nodebb-plugin-emoji issue in more detail as this is 100% a permissions issue

    4d5466ed-cbe5-4752-b90c-0b239e40b3e8-image.png

    wrote on last edited by cagatay
    #6

    @phenomlab faced same problem for upgrade to 2.8.5

    f770a39a-e568-4073-9995-576d0b6034a5-image.png

    Mark do you have this plugin on Sudonix? And which version are you running?

  • @phenomlab faced same problem for upgrade to 2.8.5

    f770a39a-e568-4073-9995-576d0b6034a5-image.png

    Mark do you have this plugin on Sudonix? And which version are you running?

    wrote on last edited by
    #7

    @cagatay Yes, I do, but it’s not a version issue - it’s permissions.

  • @cagatay Yes, I do, but it’s not a version issue - it’s permissions.

    wrote on last edited by cagatay
    #8

    @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 🙂

  • @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.


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.
  • 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/
  • 4 Votes
    8 Posts
    2k Views
    phenomlab
    @Panda said in Upgrade to NodeBB v3? 2BB or not 2BB, that is the question!: So although thats a plugin it has Widget like element and stopped working on the Theme change Which is normal based on the widgets being reset when you change themes.
  • Email validation NodeBB

    Bugs nodebb
    21
    3 Votes
    21 Posts
    10k Views
    phenomlab
    @Panda said in Email validation NodeBB: Did you configure that as a custom change to the usual quote icon. How do you do that? I notice on NodeBB site its a solid blue quotes Yes, I changed it. NodeBB by default users the free font awesome library whereas I use the pro (paid) version SDK have access to a wider set of icons, and at different thicknesses etc. The change of colour is just simple CSS.
  • Upgrade Problem from 2.8.9 to 2.8.10

    Moved Solved Configure upgrade nodebb
    15
    1
    1 Votes
    15 Posts
    4k Views
    phenomlab
    @cagatay Were any errors displayed during the upgrade process?
  • nodebb loading emojis

    Solved Configure nodebb emojis
    16
    1
    1 Votes
    16 Posts
    6k Views
    phenomlab
    @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.
  • 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
  • 0 Votes
    5 Posts
    2k Views
    phenomlab
    @qwinter this particular site uses the code I wrote if you want to see it in action. It’s a information and intelligence gatherer I designed for collecting various information security articles from around the globe and consolidating them in one place. Essentially, each “post” is in fact generated by the script, and the NodeBB API. https://hostrisk.com/