In your setup redis will be used for sessions, pubsub and socket.io will use it to pass around messages. Each nodejs process has it's own post cache, you can see the caches at /admin/advanced/cache. Redis pubsub is also used to clear cache on the other nodejs process when it is cleared on one nodejs process. For example when a post is edited it's cache will be cleared on the other nodes.

You are right. I was fixed enabling Custom SMTP and set port 25 and all parameters there: [image: JeTory0.png]

Mmhm, because we noticed it taking a long time we added progress bar support, so you can see that it's doing something We store the IP addresses going back to the installation of the forum, so it's possible that it's no longer needed. One could simply delete the entire ip:recent set with no ill effects... (well, except that you'd no longer have a historical record of recent IP addresses)

@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.

If you are only using redis for cache yes you can just flush it.

I have nginx proxying to nodebb, from a /forum/ location. I wanted to serve up static contents with nginx - the example here - https://docs.nodebb.org/en/latest/scaling/#use-a-proxy-server-to-serve-static-assets assumes you have the forum running off the root. If running from a subfolder, it can be simplified to this (the public folder is tried first, followed by the proxy if no file exists). Here's my config using nginx to serve up the static content (just the locations/configs for nodebb included, I have a wordpress site running of the htdocs root) upstream io_nodes { ip_hash; server 127.0.0.1:4567; # upstream nodebb servers here } server { listen 443 default_server ssl; listen [::]:443 default_server ssl; server_name your.site; root /webroot/of/site; index index.html index.php; location /forum { alias /path/to/nodebb/public; try_files $uri @nodebb; } location @nodebb { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_pass http://io_nodes; } }

@BuZz 1 is the correct answer,as the number of replies includes the first post in the topic which isn't technically a reply, which I think adds to the confusion. Also with the reversed logic from the 2 settings before (which are how many seconds someone is allowed to do something, rather than how many until they are disallowed)

There is a lot of settings I am using this my self. My settings is about 1 week

if the issues are not with your installation then I think the dev team prefers the github issue tracker so that they don't get lost in here.