Oh look right there in the manual that I stopped reading after the GUI was up...
Running into this: "warn: You have no mongo password setup!"
@pichalite This is the contents of /etc/mongod.conf:
# mongod.conf # for documentation of all options, see: # http://docs.mongodb.org/manual/reference/configuration-options/ # Where and how to store data. storage: dbPath: /var/lib/mongodb journal: enabled: true # engine: # mmapv1: # wiredTiger: # where to write logging data. systemLog: destination: file logAppend: true path: /var/log/mongodb/mongod.log # network interfaces net: port: 27017 bindIp: 127.0.0.1 #processManagement: #security: #operationProfiling: #replication: #sharding: ## Enterprise-Only Options: #auditLog: #snmp:
And that is it.
@Aton-Bridges did you set the mongodb password in the NodeBB config file?
@pichalite Was that something I needed to do in addition to using the web installer? Will check and see what it says...
Config.json only references the NodeBB secret.
It has the correct mongo username and database listed by not password. Should I add it there?
@Aton-Bridges That's where the warning comes from. NodeBB checks the config file during startup and warns you if it doesn't find a password. Add the password in the config file.
@pichalite On the money! Thanks.
@Aton-Bridges that eliminates the warning from NodeBB but I don't think your MongoDB is actually authenticating using the username and password. I am not too familiar with MongoDB. May be someone who knows it can respond on how to make it authenticate.
@pichalite Any thoughts on how I can test to see if it is or is not authenticating?
@pichalite Okay, this fixed the error outputs (w correct version of 3.0.1) but
./nodebb startstill produces this output and returns the shell.
$ ./nodebb start Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb restart" to restart NodeBB $
Something to worry about or no?
./nodebb logruns fine it seems...
@Aton-Bridges that's standard output of
./nodebb startwhich means everything went fine during startup
@pichalite So its running in the background?
Well, damn. Didnt know that.
Okay, Thanks for your phenomenal help, @pichalite.
Gonna mess around with this proxying and nginx a bit now that everything is moving forward again.