Community

@ᴅᴀʀᴛʜ-ᴠᴀᴅᴇʀ It probably crashes because of the plugins you installed and nodebb can't find them (nodebb-theme-oxide in particular)

I suggest you backup the redis database by copying the /data folder somewhere, then delete the contents of the original folder and also remove the config.json volume.

Erase and restart redis and nodebb container (It should be like a fresh install) then installs the plugins and themes listed in the log file (nodebb-plugin-teamspeak-verify, nodebb-widget-search-bar, nodebb-theme-oxide, etc)

When all plugins are installed and enabled, stop the nodebb container and restore the /data redis database with your backup, and remap config.json volume and I think it should be up.

Next time you want to upgrade, disable all plugins before restarting the container with the new image.

Problem solved, for the record I have added all file on my GitHub: https://github.com/LM1LC3N7/Dockerfiles/blob/master/nodebb/README.md

Try the Ubuntu docs instead of the Debian docs. They're more up to date.

I am spinning up a new community and found the following warnings during my install.

Anything I should do about these?

[[email protected] ~]# 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 [[email protected] ~]# cd /opt/bnacmty/ [[email protected] 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. [[email protected] bnacmty]# cd nodebb [[email protected] nodebb]# npm install npm WARN deprecated [email protected]: use uuid module instead npm WARN deprecated [email protected]: 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 [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to [email protected]^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. [email protected] /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?

Here's how I got NodeBB up and running on the Google Cloud Platform.
The following are the steps I took:

Created VPC firewall rule with 4567 port.

Deployed Compute Engine VM Instance with Ubuntu Pro 20.04

Install NodeBB via the Web Interface.

Install Let's Encrypt Wildcard SSL on Nginx.

The documentation for setting up NodeBB on Compute Engine can be found here.
[Installing NodeBB on Compute Engine] (https://www.incapio.com/post/install-nodebb-forum-on-compute-engine-google-cloud-gcp)

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 : )