Great! 
@frissdiegurke Thanks for the debug -- it's an unusual scenario, and has actually been in the NodeBB docs since the earliest commits*, but was removed perhaps a month ago because it's not a typical use case.
What I imagine happened was @lukelarris installed the package "node", instead of "nodejs":
Package: node
Amateur Packet Radio Node program
The node program accepts TCP/IP and packet radio network connections and
presents users with an interface that allows them to make gateway connections
to remote hosts using a variety of amateur radio protocols.
If you install "nodejs" on top of that, the executable becomes "nodejs". apt-get remove node followed by apt-get install nodejs does not restore the proper paths, either, the correct steps are:
apt-get --purge remove nodejs nodeapt-get install nodejs* It's been in the docs "since the earliest commits" because when I first tried installing Node.js, I typed in apt-get install node 
@julian but shouldn't it be easy to add this case? just test if which nodejs results sth., otherwise use which node and assign it to a variable... then use this variable instead of node command. I think to have which as dependency isn't to much pain ^^
As long there are no naming-conflicts with nodejs it should work 
See, I mentioned it here at the end of the install steps in the README
... but of course, it's gone now -- I wouldn't mind adding it back into the Ubuntu/Debian install wiki page
Yup, I can have loader.js check which executable to run. Shouldn't be too difficult... #1449
@julian I don't know what you wanted to do in loader.js, but #1450
@julian didn't install the node package, only installed nodejs, redis, and npm. It might have been installed with npm but idk.
@julian just notice that the github-embed plugin displays 'open' even so they're closed for 4h now, is this an issue of github somehow or does your plugin fail?
@frissdiegurke said:
@julian I don't know what you wanted to do in
loader.js, but #1450
Every time I've found nodejs in the wild it was the crazy old stock version of the distribution. Sticking to the node command sounds kinda good to me.
@frissdiegurke I don't hammer the API, so my plugin uses an lru-cache and expires stale entries after one day.
I imagine this is better if it were configurable, and to a more sensible default (perhaps default 2 hours?):
Edit: God damnit, my plugin doesn't like dashes either, it seems.
@lukelarris I run into the same issue in 14.04 server too. You need to install nodejs-legacy through apt and it's running well then
