Try the Ubuntu docs instead of the Debian docs. They're more up to date.

@PitaJ thanks. I need to install it on Heroku and it doesn't have nginx now. I know I have a long road ahead, but I think I found the direction.

@JaredBusch Thanks. Really appreciate it

@sebastian-marinescu alternatively you could set defaultPlugins as an environment variable, then run ./nodebb setup [config json]. I'll re-add an actual option for passing in a set of default plugins.

@countach said in "NodeBB could not connect to your Mongo database" Error: @baris thats the thing I do not get that prompt to specify the DB, it attempts to connect automatically after ./nodebb setup is executed. Could it be the authentication settings? I have security authorization enabled in my mongod.conf ... If you had an existing config.json, it will only try to fill in blanks. Try moving your config.json out of the way and running it again. It will have prompts like this... 7/7 01:07:24 [3009] - info: Now configuring mongo database: Host IP or address of your MongoDB instance (127.0.0.1) Host port of your MongoDB instance (27017) MongoDB username Password of your MongoDB database

Eh, try LXC. I recommend it over Docker

Latest version of NodeBB doesn't require this dep anymore, so maybe try pulling the latest master?

As @pitaj mentions, invoking sudo with NodeBB is bound to bring you trouble -- no need for superuser privileges for NodeBB, and I'm thinking of having NodeBB run as the nobody user, if possible...

@julian It seemed pretty straight forward in my mind is the worst part. Yup, I want this server to be this other server's pathetic little slave and take orders all day...Wha?.....It's rebelling! It's hard to beat the incorrect logic of something you know absolutely should work as you're telling it to.

@julian, I think I fixed this issue. I rolled back to a snapshot before I installed NodeBB and re-cloned the 0.5.1 branch and it installed without an issue and I have sweet, glorious CSS!

@julian Thanks, now it's no problem : )

Fixed, I did not uninstall 2.4 properly, this guide helped me Thanks!