Nevermind I fixed it with the session-sharing plugin. I set it to revalidate instead of trust.

@julian Unfortunately I ended up nuking the repostory and rechecking it out mulitple times trying to fix it. In the future I know I can't trust the database entirely. I'll have to backup all the files (that I thought were ephemeral).

@scottalanmiller said in No Code Button?: Like that code button? [image: MU8d3Tk.png] No like this [image: 9PLCGKi.png] Yes, I know you are showing the same thing. but You did not highlight it.

We haven't figured out why this is happening yet, relevant GH issue https://github.com/NodeBB/NodeBB/issues/3200

I know this post is a little old, but I wan to know if it is resolved since I have the same situation

Ok, when I switched to using a clustered setup with nginx serving static assets this issue went away.

They have to go into their user profile settings and select the group, even if they only have one. Yeah, let me add this as an issue to our tracker, happened to forget about this EDIT: https://github.com/NodeBB/NodeBB/issues/3118

For anyone else that may find this post and is struggling, this step by step walkthrough really helped me out (at least regarding the php oauth2 server) http://bshaffer.github.io/oauth2-server-php-docs/cookbook/

Welp, I solved it. Turns out I had the wrong directory specified in nginx for static assets. It was pointing to a different install of nodebb. For some reason that caused issues with socket.io (and only with safari/opera for some reason). Now, here's the weird thing. I only recently started using nginx to serve the assets. Recently as in like this morning. Before that I simply had a proxy pass setup and let nodebb serve the assets. I'm not sure what was causing the 400/502 errors then but I'm just glad their solved now.