We highly recommend you stay up to date for the latest security fixes.
This looks more like a cacheing issue though. You can try running a rebuild and restart, that should reset the cache buster.
I can't really tell if I'm experiencing the same situation, however, every now and then after about 24-36h NodeBB randomly ''dies'' & when it does that, it displays error 502, which I can only resolve with rebooting the VPS. I'm also running it with nginx proxy & NodeBB is started on every reboot using
./nodebb start in an
Sorry for bringing up this old post, but I've been struggling with the problem for almost a month now. I've tried many things - rewriting the start script, checking the logs for any error output etc. etc., nothing has helped so far. So I started thinking, that maybe the small amount of RAM is the reason for those unusual ''crashes''. So without doubt, I went for a 1024MB DigitalOcean VPS. And indeed, this improved the situation, however the NodeBB still crashes every now and then, but not on a daily basis anymore.
So I'm thinking that maybe there is a memory allocation problem with NodeBB or just NodeJS? I'm on NodeBB 0.4.3, not on the latest build ofc.
I'll do some tests and write back with some RAM allocation results.
@a_5mith It's harmless, especially if you're not using all that extra disk space in your droplet.
When we were running this forum on a $5 droplet, we also ran php-fastcgi and mysql. MySQL would run out of memory every couple days because we didn't have swap enabled.
Keep in mind that when Redis holds all of the db information in-memory, it also needs twice that amount when it tries to persist to disk. It makes a copy of the in-memory database, in memory (heh), and then pushes that to the