What’s going on with NodeBB?

[phenomlab]

@cagatay That is quite the jump as importers from one forum platform to another are notoriously unreliable and could land up being quite costly if it requires managed services.

[cagatay]

After the latest update, my entire system crashed and I’m unable to bring it back up.

[phenomlab]

@cagatay what is in the nodebb log?

[cagatay]

[cagatay]

I downgraded the version, and now it is working. I think the issue is related to the version.

[DownPW]

@cagatay said:

I downgraded the version, and now it is working. I think the issue is related to the version.

Maybe yes, maybe no. it can be plugins compatibility, nodejs, npm etc.

I don’t upgrade for now. I still waiting a little before upgrade.
I’m on 4.10.3

[phenomlab]

@DownPW I tend to stay at least one release behind intentionally to ensure maturity before upgrading - unless there is a good reason to do so immediately - such as identified vulnerabilities

[DownPW]

That’s exactly our approach on PW now. Learned it the hard way , upgraded too early once or twice and paid the price. Actually sitting two releases behind at the moment, not just one. Stability over bleeding edge, unless a vulnerability forces the hand. Solid policy.

[cagatay]

To be honest, I really regret moving to NodeBB. I should have stayed with XenForo.

[DownPW]

Honestly, I don’t regret the move at all on my side but I get that the experience can be very different depending on how comfortable you are with the technical side. XenForo is definitely more forgiving if you don’t want to deal with the server.

One thing worth keeping in mind though: your install has some custom code on it, and need to know what it does or stay to stock nodebb witout modification

What’s actually frustrating you the most right now? If it’s day-to-day admin stuff, there might be simpler fixes than rebuilding everything on XenForo.

[cagatay]

I don’t want to keep worrying about whether the script will break with every update. Yes, we invested a lot of effort, yes, I have custom code, and yes, everything works well but somehow I end up facing issues after every update. And honestly, I think they have a development approach that doesn’t really listen to users. They just add or remove things based on their own ideas. The social plugins were a complete disaster

[cagatay]

how to upgrade nodejs v20 to v22?

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

1. Install Node 22:
   nvm install 22
2. Switch to Node 22:
   nvm use 22
3. Set it as your default:
   nvm alias default 22
4. 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.

1. Remove the old NodeSource list (optional but cleaner):
   sudo rm /etc/apt/sources.list.d/nodesource.list
2. 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 -
3. Install/Upgrade Node.js:
   sudo apt-get install -y nodejs
4. Verify the installation:
   node -v

---

Method 3: Using the ‘n’ Package

If you have npm installed, you can use the n interactive manager.

1. Clear the npm cache:
   sudo npm cache clean -f
2. Install the ‘n’ helper:
   sudo npm install -g n
3. Install Node 22:
   sudo n 22
4. 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.