I think after release of every version / tarball you must hand it over to QA, now I understand this will be messy for you guys to handle so lets form a group for people who want to volunteer on the same.
I would love to volunteer, I'm gonna use code created by you, consider it as a thank you
And yes @julian I want to write an aerospike connector for nodebb, its way faster than mongo and more reliable than redis
We also require a better way to upgrade the forum (maybe a script that has to be run - for copying attachments and stuff and taking db dumps , then after installations reloading from the dumps and in case of errors falling back to the prev version)
It seems that some users had to clear cookies (and maybe html5 localstorage) to get pass the Forbidden error, even after it was fixed for me. When I was having the problem initially, clearing cookies didn't seem to help, but at least one form of the error is due to having outdated cookies. This may have been caused by changing the secret key in config.json.
Thank you @markkus and @jarey for your replies. I did what you suggested about re-installation and the problem persisted. I then discovered something...
...the installation manual may be outdated. The file in question on Step 7 is mongod.conf instead of mongodb.conf.
Can @psychobunny or whoever in charge of the Doc double check this and make the proper correction?
As I am a irreparable idiot, in the pursuit of messing with my Lavender/Persona hibrid theme I in some likely unrelated way totally destroyed everything.
I was messing around with CSS, hit restart, and the server went down, hard. And hasnt come back since. I've tried restarting the server, running nodebb resets for widgets, themes, and plugins, restarting nodebb what must be 50 times.
The log output I'm getting is:
Clustering enabled: Spinning up 1 process(es).
26/7 19:57  - info: Time: Sun Jul 26 2015 19:57:53 GMT-0400 (EDT)
26/7 19:57  - info: Initializing NodeBB v0.7.1
26/7 19:57  - error: [meta.dependencies] Could not read: nodebb-plugin-spam-be-gone
[cluster] Child Process (1252) has exited (code: 0, signal: null)
and when I try to access the page, I get a:
This webpage is not available
I assumed this was a redis issue, so I tried restarting redis to no efffect, I know I disabled the emoji plugin so tried to reinstall it via SSH but it didnt help.
Any suggestions for getting this back up and running?
Edit 1: Tried running npm install to see if it could be some update issue, will update with results.
Edit 2: running npm install appears to have fixed it. Future people with this issue, use NPM install and dont be an idiot like me resetting everything.
I keep getting this error when i finish my ./nodebb setup im on centOS linux 64 bit
nodebb could not connect to your mongo database mongo returned the following error: auth failed
then the setup just gets aborted and when i do sudo service mongod start , or stop it just returns failed... heres the Mongo start failed , stop failed Mongo failed
and here is the error i get when i do the nodebb setup nodebb setup error any help would be great
Thanks for all the help!
For anyone else with this issue, the end solution was setting up the server via SSH not using the web console, shutting down nodebb with ./nodebb stop
sudo apt-add-repository ppa:chris-lea/redis-server
sudo apt-get update
sudo apt-get install redis-server
to update redis, then starting nodebb back up using
NodeBB is designed to work best under a virtual private server. Using a traditional hosting service is not recommended as they do not have the capabilities to power NodeBB effectively.
The code and instructions can be found here at our project repository
Full instructions can be found in our Documentation Portal
We recommend DigitalOcean to host your NodeBB, you'll get a month free just by registering with this link. You can also try applying the 10TOSHIP coupon to get another two months free.
Thank you for your interest in NodeBB!
To answer your last query, NodeBB supports both
Thank you to both of you
Ensure that the config.json still points to the same database... if it's a blank site, then NodeBB is reading an empty database...
Before upgrading, config.json was pointing to Redis DB 0. After upgrading, it's still pointing to Redis DB 0. The configured Redis password still matches.
So not sure, how to proceed from here.