@ᴅᴀʀᴛʜ-ᴠᴀᴅᴇʀ 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.

Yes I'm referring to the Dockerfile. I'm no expert with Docker either, but I must admit that it's extremely handy for creating forums on the fly with different versions at the same time, and saves a lot of time. If you're not focused on this tool I completely understand and appreciate you already providing up-to-date docker images, so I'll try to see what I can do myself and share it if it works well. This is possible by manually modifying the dockerfile but I think it's also possible in a more elegant way and easy to use, with env variables

Hello, I have enabled emailing of forum news summaries (What's new? emails) But the sending time at 7:00 doesn't suit me, so how do I change the sending time of these mails? Thanks.

it works, thanks for all your answers, I'm reassured.

Yes, something like that

Hello, With Spam be Gone I noticed that implement standard recaptcha from google is super easy, butI haven't been able to install Invisible reCAPTCHA that doesn't even display the "I'm not a robot" dialog box. If in the future nodeBB could support it, it would be great. Thanks.

@pummelchen Thanks for the response. Ok for the solution, but If that's true, it's still strange behavior. My forum is in a test period so indeed it doesn't have much traffic, but I come by at least once a day to see just how frequent the error is. It means that if we go on vacation and nobody visits our forum for a few days, when we get back all the owners of a forum under nodeBB have chances to see this error? That's annoying.