I figured out my problem. I set up forever incorrectly. I think somehow after a server reboot it didn't load NodeBB the way it should. Is this possible? I built maybe 20 instances to figure out what caused my problem.
Thanks for the hard work on the project!
I'm checking back in from a while ago. Since the first post I've moved VPS's from digital ocean to ovh and now I'm moved to vpsdime. I highly recommend them. They say the large storage vps IO is too slow for production but so far it has seriously been 10x faster in disk benchmarks and 20% faster in cpu calculations.
Anyway, back to what I was going to say.
I started nodebb using a root cron
@reboot forever start /home/blue/nodebb/app.js
turns out this gave me the button errors.
This method works without issues
@reboot cd /home/blue/nodebb && forever start app.js
Interesting huh? Hopefully this helps someone avoid the headaches I've encountered. Any ideas why this may be?
I installed v0.6.x-dev which may have been the cause. Also, I may not have ran "npm install -g forever" in the nodebb directory. I'm not sure if this would make a difference?
Forever is working fine with v0.5.4 and installation using "npm install -g forever" in the nodebb directory.
I execute Forever using this cron job.
@reboot cd /home/nodebb && forever start app.js
I'm sorry, I should have written that.
I just fired NodeBB up again with Forever. At login it says
"Failed login attempt, please try again.
Invalid Password"
And when I stop NodeBB with forever and start it again (with sudo ./nodebb start) it works.
This is cross browser. (IE, Waterfox, Chrome)
Also, I had another very weird bug on Digital Ocean experimenting with Forever and NodeBB but I can't recall the specifics. (Things weren't loading.) I'm on an OVH VPS right now.
Thanks for your hard work!
Using Forever to start NodeBB causes account logins to fail
Ubuntu 14.04
NGINX 1.4.6 Proxy
Redis 2.8.4
NodeBB v0.6.x-dev
Everything works fine when using ->
sudo ./nodebb start
OR
sudo ./nodebb dev
I setup and ran Forever with the following ->
sudo npm install -g forever
sudo forever start /home/nodebb/app.js
Possibly I am doing something wrong?
Is there another recommended procedure to start NodeBB on reboot? What do you guys use?
I installed nginx and used it as a proxy. It seems to work now. I couldn't figure out what may have been wrong.
I tried older versions of NodeBB and that did not resolve the problem. I have a feeling it's something to do with apache and the way I was setting it up. I'm using virtualmin.
*Setup which did not work
Ubuntu 14.04
LAMP
Virtualmin
Proxied using these settings in Virtualmin
MENU NAVIGATION: webmin -> server -> apache -> server name -> Edit Directives ->
<Proxy *>
order deny,allow
allow from all
</Proxy>
ProxyPass /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket
ProxyPassReverse /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket
ProxyPass /socket.io/ http://127.0.0.1:4567/socket.io/
ProxyPassReverse /socket.io/ http://127.0.0.1:4567/socket.io/
NGINX fixed my problem. I am including this information for others reference.
For some reason topics do not display while logged in.
They work fine while not logged in. I cleared browser cache, and tried IE Firefox and Chrome.
This is a fresh install.
VPS Ubuntu 14.04 LAMP setup using Apache as a Proxy. I wonder if the proxy is the issue.
Thank you for your time,
Tad
Hmmm, it seems to have broke again. It will run for a while without issues and then I will come back in an hour and the buttons don't work. It's strange.
I figured out my problem. I set up forever incorrectly. I think somehow after a server reboot it didn't load NodeBB the way it should. Is this possible? I built maybe 20 instances to figure out what caused my problem.
Thanks for the hard work on the project!
I also have the same issue. New install v0.5.0 although I may have missed a step in the install process.
NodeBB v0.5.0
node.js v0.10.32
Redis 2.8.4 32bit
Ubuntu 14.04 32bit
edit - the admin panel is working
I'm running a digital ocean test droplet. Nginx and Apache are only required for proxy requests, correct?