I am spinning up a new community and found the following warnings during my install. Anything I should do about these? [root@bna-com ~]# nvm install v7.2.0 ######################################################################## 100.0% Computing checksum with sha256sum Checksums matched! Now using node v7.2.0 (npm v3.10.9) Creating default alias: default -> v7.2.0 [root@bna-com ~]# cd /opt/bnacmty/ [root@bna-com bnacmty]# git clone -b v1.x.x https://github.com/NodeBB/NodeBB nodebb Cloning into 'nodebb'... remote: Counting objects: 112796, done. remote: Compressing objects: 100% (101/101), done. remote: Total 112796 (delta 38), reused 2 (delta 2), pack-reused 112693 Receiving objects: 100% (112796/112796), 34.86 MiB | 9.87 MiB/s, done. Resolving deltas: 100% (84665/84665), done. [root@bna-com bnacmty]# cd nodebb [root@bna-com nodebb]# npm install npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years. npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. nodebb@1.3.0 /opt/bnacmty/nodebb

Definitely seems like cache issue with the record for express-session. try sudo npm cache clean? After that try manually clearing the cache files?

ok, I think I solved it. Apparently, after executing commands like sudo firewall-cmd --zone=public --add-masquerade --permanent sudo firewall-cmd --zone=public --add-forward-port=port=80:proto=tcp:toport=8000 --permanent sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8000 somewhat screwed up the firewall rules in the google console. The catch was that I could only acces the website from port 80, by trying to acces it from 8000(node's actual) didn't work. I deleted the rules, and added them again in the platform console (Networking->Firewall rules) and then restarted nodebb and it worked!

Fixed by reinstalling redis-server.

Thanks!! #closed

Thank you for your support

@ChaosYamYT This plugin is incompatible with current versions of NodeBB. You could try opening an issue at the Github repo for the plugin, and asking the developer to fix it.

@a_5mith True, but honestly, it's easier to set up a quick Linux VM (and I say this as someone who is not at all a fan of Linux) and the support is far better.

@jimmerz213 said: <stuff> So I just built a quick VM locally and followed the guides I mentioned above. Did nothing differently except I didn't install php and apache before and start ripping things out. It works flawlessly. I can only imagine at this point its something with my server and I think I may just wipe it and start clean, using nginx only instead of apache. Thanks for looking at this stuff guys - I appreciate it. Edit - welp, it works great now. Probably has this whole time. The URL I was using to hit the forums was set to be x.x.132.x, it had to be x.x.135.x. Hey, at least I learned a TON about nodebb and nginx I'll take it.

@julian That's got to be it, thanks mate!

noticed it here too. I'll update and see if it fixes.

nothing is listening on port 80 except my nodebb ip.

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