What version of nodebb are using ? Can you please tell me what's the result of

npm ls nodebb-theme-vanilla

Sorry I don't understand neither speak german.

I guess you're using Apache, so you need to use it as a proxy for nodebb. Install mod_proxy_wstunnel for apache 2.2 https://www.amoss.me.uk/2013/06/apache-2-2-websocket-proxying-ubuntu-mod_proxy_wstunnel/

and add this for example in your vhost file in apache (/etc/apache2/sites-enabled/000-default ?):

<VirtualHost *:80>
    ServerName yourdomain.org
ProxyRequests off

<Proxy *>
    Order deny,allow
    Allow from all
</Proxy>
ProxyPass /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket retry=0
ProxyPassReverse /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket

ProxyPass /socket.io/ http://127.0.0.1:4567/socket.io/ retry=0
ProxyPassReverse /socket.io/ http://127.0.0.1:4567/socket.io/

ProxyPass / http://127.0.0.1:4567/ retry=0
ProxyPassReverse / http://127.0.0.1:4567/
</VirtualHost>

I have got the same problem as @Tanner. I'm running the version 0.5.2, disabled all plugins, restarted nodebb and cleared cache.

I even tried a git reset --hard HEAD, but not all "save" buttons works in the ACP. It seems to actually works in core options and some plugins, but not in many plugins settings like Facebook SSO, Steam SSO, Twitter SSO, Blog Comments.

Any idea what could cause this?

Try this https://community.nodebb.org/topic/2614/solved-issue-with-some-plugins-in-acp-v0-5-2/7

Don't worry you don't bother me @peter. You simply need to execute those commands:

./nodebb stop
git fetch
git checkout master
git merge origin/master
./nodebb upgrade
./nodebb start

What is the "url" in config.json?

You can try.

npm remove nodebb-theme-vanilla
npm install nodebb-theme-vanilla

Happy Easter guys!

Ok, well you are using the master branch with 0.7.0 and the plugin spam-be-gone is not compatible with it I guess. About flip theme it seems that it's not compatible with 0.7.0 as well. For the lavender theme, you can update it to its lattest version with npm.

npm -i nodebb-theme-lavender@1.0.8

It's a bit off-topic but still related to default settings for external links. I haven't tested the acp of 0.7.0 yet and I was wondering if there was something like a whitelist for external links? Then if someone click on an external link we can activate the warning page "you are leaving the forum", but if it's a sub domain, a root domain or a trusted url (youtube) for example we don't show this page.

Happy Easter guys!

I imagined something like that for filtering by categories. The active tab would be bigger than the others.

That would be awesome. A sorting system with tabs to show only posts by categories would be nice as well if it's possible.

I confirm it, I tested on Chrome and Firefox for android.

What is the "url" in config.json?

Ok, well you are using the master branch with 0.7.0 and the plugin spam-be-gone is not compatible with it I guess. About flip theme it seems that it's not compatible with 0.7.0 as well. For the lavender theme, you can update it to its lattest version with npm.

npm -i nodebb-theme-lavender@1.0.8

What version of nodebb are using ? Can you please tell me what's the result of

npm ls nodebb-theme-vanilla

You can try.

npm remove nodebb-theme-vanilla
npm install nodebb-theme-vanilla

Yes sure. I've got a backup of the db and nodebb from 0.5.7. As you think it's a db issue. Does it worth it to try to upgrade it again from this version?

Edit: I restored the backup (0.5.7) of nodebb and the db, upgraded again to 0.6.1, I tried several times. It's still the same. I also tried to upgrade from 0.5.7 to master, and still the same. Always getting those websockets error in the browser console

Edit 2: Alright so this time I tried a fresh install of nodebb with a fresh db. I can see all the default categories created by nodebb this time but I still see the websockets error in the browser console and still have got the same issue in the admin certainly to do websockets failing.

Now I know it's not an issue with the db or the upgrade (I think) but maybe with the proxy in apache even with this https://community.nodebb.org/topic/3509/upgrade-to-0-6-x-issue/12 , it wasn't working. I precise that I've got apache 2.2.22 with wstunnel (more recent) backported.

Edit 3: I directly accessed nodebb without going through apache proxy. I had no errors so I could have fixed the categories permissions. I still need to know why the proxy reverse can't handle websockets anymore after having upgraded nodebb.