@pitaj great! This is what I am looking for. And you understood it even though I wrote it wrong. Actually I would ask for ./nodebb upgrade --series but a config option is much better. Thank you! It would be great if you could include this option in the documentation.

@pitaj Thanks! With node v8.7.0 and npm v5.4.2, I was able to run ./nodebb upgrade and now I'm a proud member of the nodebb v1.7.4 club. [image: tenor.gif]

Thank you @PitaJ and @baris ! It was the plugin. I had installed the 1.2.1, but it does not worked. I uninstalled the plugin and registration i working fine again.

Thank you @PitaJ and @julian for your support! Everything works fine now. The error was because of a wrong security option in the settings and the speed of sendmail increased by itself. Probably there was a problem on the shared server during my first test. Keep up the great work! NodeBB is really great!

Hi guys, i'm looking for a solution to invite about 200 people at once to our forum. I tried the built in invite-feature with a comma separated list of emails, but this does not really work. In this case nodebb is generating only one email with one invite-URL and one token for all recipients and all addresses are shown transparent in CC-field of the email. I tried also to install the nodebb-plugin-user-invitations, but the plug-in doesn`t work with nodebb 1.5.3 any more, at least in my setup...I remembered the bulk invitation feature of the plugin and would test it again, but unfortunately it does not work anymore. I tested the plugin a few ago with 1.5.0 (or less) and uninstalled it, because we did not really needed it and recognized some problems with the core invitation system after a while and 1 or 2 updates of nodebb. After uninstalling the plugin the invitations from the core function worked well again. Does anybody know if there is another way to invite more the one user at once? Thanks a lot for your help, Chris

@suparomana said in Websocket connection problems via ssl on special port: Apache 2.2 can not handle websockets Ahh, thanks. Okay, that makes sense now. It sounds like it's failing because of the special port. Since that port is sending directly to NodeBB and not through the Apache proxy, NodeBB does not know the SSL key, so it will fail the connection. I think there used to be a way to feed the SSL Key path to NodeBB in config.json, but I don't see any docs on it anymore, and I'm not even sure if that would work. I think your best bet is to try getting websockets to work through Apache2, there seems to be several methods even though there's no official support. https://serverfault.com/questions/290121/configuring-apache2-to-proxy-websocket