This is happening since the code to get the version was moved to the server side, https://github.com/NodeBB/NodeBB/issues/6540barisusakli created this issue in NodeBB/NodeBB open cant lookup latest version #6540
Error in console.
I tested npm on my vps and accidentally deleted something, now the forum does not want to start and the console displays a bug visible on the screen. I tried the ./nodebb build and ./nodebb setup commands, but they do not help.
sudo ./nodebb setupor
sudo ./nodebb start
@paopevil I always run nodebb from sudo.
EDIT: I fixed the error by replacing nodebb files with new ones and running the ./nodebb upgrade command.
@rikodev you really shouldn't
@pitaj Why I shouldn't do that? Other attempts to correct this error did not work.
Did you mean to run NodeBB through sudo? There are no errors when running the forum without sudo, so sudo is no longer necessary.
@rikodev yeah, please don't install or run NodeBB with sudo.
Why shouldn't I use
sudoto run NodeBB?
You do not want to run NodeBB using
sudobecause this causes NodeBB to be run via the
rootuser. This superuser has complete access to the entire system and should NodeBB ever become compromised, then a malicious user can utilise NodeBB as an attack vector to take over your system.
Secondary effects from running NodeBB under
sudoinclude the changing of ownership of some files to
root, which would complicate administration of your NodeBB further as future starts of NodeBB will fail with an
EACCESerror, simply because some files could not be written to, as they are now owned by root instead of the regular user!
Best practice security recommends running NodeBB with as few privileges as possible (ideally,
nobody:nogroup), but practically an unprivileged user is perfectly fine.
By the way, this also means running NodeBB as a user that has sudo access is also insecure. Just some food for thought.