you need to use v 0.3.1 for nodebb v1.4.5

npm i [email protected] --save

for http://retropie.org.uk/forum/ we have around 3-5k page views per hour. Running with mongodb, redis, and nginx as a front end proxy with currently 4 nodebb processes (I recently reduced it from 6 and it seems to manage well). nginx serves up the static content.

Server is a VM with 4gb ram and 2 cpu cores.

@torn2 because they referenced an external CSS which was updated to v4.0 (bootstrap) which broke existing skins that were built on v3.3.x

I saw the "minimum reputation" settings for the user profile. Apologies but I had missed this. I will use that to restrict the spammers user of the user profile info.

I suspect a setting for X posts before they can change this info might be more suitable than reputation as we want to distinguish spammers from users, rather than the quality of users posts etc.

I run a forum with currently 4 nodebb processes which are proxied to from nginx, with a mongodb database backend and redis enabled (which from my understanding is used for sessions only in this configuration).

In this configuration every nodebb process eats a fair amount of memory (to note it was reduced significantly with one of the recent versions. 1.15.x I think - I did see some cache related changes).

Please correct me if I'm wrong, but is each nodebb process in this configuration handling its own post cache etc?

It would seem like a good idea to be able to use redis as a cache backend on top of mongodb - but perhaps I am way off how it works. My knowledge of the codebase is very limited.

[Edit] I forgot to say, thanks very much for your continued work on this excellent forum software. Is it possible to make a donation as I've been running it for 4 years for our project and am not on a paid plan etc.

1.12.0 to 1.12.1

Realised no email was getting sent from my NodeBB after an update to 1.12.1

Checking the logs it was trying to connect to localhost on port 587. However by default exim4 only listens on port 25, so NodeBB must have changed this (or the default plugin nodebb uses for sending email).

I couldn't see this documented anywhere but it may affect other users so mentioning it here.

On Debian I changed /etc/default/exim4 to include

SMTPLISTENEROPTIONS='-oX 25:587'

Might be worth mentioning this somewhere if it's not already been done.

the hashing finally completed. I am still interested to know how much data may be stored here, as it took 2 hours to complete. Not sure that much "recent" ip data is needed.

It's still processing - I'm inclined to stop it and restore the db backup until I have verification on this. Certainly if it is something that should take this long, it would be useful if it had some sort of progress bar.

Am currently updating to 1.10 (from 1.9.x) and it's taking a very long time with

4. Updating NodeBB data store schema...
Parsing upgrade scripts... 
OK | 4 script(s) found, 53 skipped
  → [2017/6/22] Hash all IP addresses stored in Recent IPs zset...

(Mongodb 3.4.15)

I assume it's going through a very large number of ips - as cpu usage is high and it's still processing. It's taken over 30 mins so far. Is there any way of checking on progress manually via mongodb cli ? Also how can I see the size of the data set ? I wonder if the list of ips stored is larger than it should be due to the time taken.

@julian Using the registration queue would add a lot more work for admins/mods though - but certainly it would help with this also.

Looks like the above has helped, but we are still getting some registrations - the spam accounts are now just putting the URL in the "Full name" field.

I suspect a setting for X posts before they can change this info might be more suitable than reputation as we want to distinguish spammers from users, rather than the quality of users posts etc.

I saw the "minimum reputation" settings for the user profile. Apologies but I had missed this. I will use that to restrict the spammers user of the user profile info.

I use the anti spam plugin which helps with posts, but I have noticed recently a large number of spammers registering and using the user info / profile page to create an "Advert" for their services. They are not posting, just creating profiles which link to their website etc.

I don't believe this feature exists, but it would be useful if you could specify a user to not be able to set up a user profile info page until they have X posts or similar. This should stop them being able to do this.

I may open a ticket for the spam plugin to also send the profile info to akismet as I suspect it doesn't do that currently.

Any ideas are welcome. Going to go and delete the 20+ new spam accounts now that have appeared in the last 2 days.