Hi,
The issue is clear from the log:
npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.25"})
npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.25"})
npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.25"})
npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.25"})
I am doing this when I run npm install forever -g
Any help how to fix that ?
@xpcontact Have you tried npm update yet?
Thank you again! it did not help 
Have you tried running forever? I have tried on my server and it works fine with those warnings.
Try forever start app.js and it should run fine.
forever start app.js
I get this error:
w9forum@w9forum.com [~/public_html]# forever start app.js
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: app.js
@xpcontact You will need to run this from within the NodeBB folder. Once it has ran it should give you the command line back and NodeBB will be running in the background.
@xpcontact said:
forever start app.js
I get this error:
w9forum@w9forum.com [~/public_html]# forever start app.js
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: app.js
Those are not errors, those are just warnings. It should be running fine now. Try forever list to see if your process is running.
Thx, yep I made sure that I am running it within the same folder (as nodebb) as I extracted nodebb files in the public_html
@ Scuzz I run forever list ;
info: Forever processes running
data: uid command script forever pid logfile uptime
data: [0] n-1Q /usr/local/bin/node app.js 18881 18883 /home/w9forum/.forever/n-1Q.log 0:0:9:12.763
data: [1] QJWt /usr/bin/node app.js 10022 10024 /home/w9forum/.forever/QJWt.log 0:11:41:26.833
@xpcontact looks like you have two forever processes running, then.
