I managed to debug what was going on and I discovered that NodeBB was doing everything correctly and that passport was working as it should, sending the right URL to redirect to, but my HTTP Reverse Proxy (In my case a IIS server) was somehow rewriting the Location header to use the servers domain.
Managed to fix this by going into the Server settings, Application Request Routing and on the right going to the "Server Proxy Settings", and once there unchecking the "Reverse rewrite host in response headers" checkbox.

@gorgiselkov The integrated Node.js web server? I believe you shouldn't do that, and as the guide states, you should always use a proxy server like, in my case IIS, but as the official guide states, Nginx.
You should follow this guide in case you haven't (depending on your Servers OS):

Index - NodeBB Documentation

@Ne-Ho I believe I have managed to fix it in my custom fork of the Material theme:
https://github.com/geferon/nodebb-theme-material

So far it works well on my forum without the page not refreshing/etc

@Ne-Ho Okay, I do have the chat Issue, i'll try to fix it, but I don't have the navigation toggle issue? I mean, is the sidebar on the left not positioned correctly for you, or what exactly is the problem?

@Ne-Ho Yes I got it already but thanks.
I've already almost managed to fix it on my end, just doing final touches and i'll publish it before going to bed.

I haven't been able to post it yet as i'm very occupied but I will when I can

@Soarin Can I have the exact error of the logs?

@Soarin It should appear, strange.
Maybe you uninstalled it by accident?

Sorry for taking so long to reply.
So, thing is I fixed the code on the openid passport provider manually changing a couple of lines.
I've started looking around to see if someone did the same as I did and, someone indeed has here: https://github.com/elendirx/ignum-passport-openid
They even added more features and fixed more things

Now, thing is that the passport-steam should use that openid passport instead of the original one, as that one doesn't support the returnURL parameter and else (which is required for the CSRF token). So, i'm going to see if I can find a package that supports the new OpenID passport and if so, i'm going to make a new plugin for the Steam login of NodeBB and publish it on NPM.

@Soarin Steam Authenticator works perfectly fine for me on 1.12
Are you sure it's not your problem and it's the new versions problem?

Edit: Actually it didn't work at first because of the CSRF token and the OpenID provider not providing the CSRF token upon login.
When I get home i'll publish my fix here.

@Ne-Ho All of those errors should be fixed, I just published a new update. Let me know if there's any other urgent issues.

@Ne-Ho Yes I got it already but thanks.
I've already almost managed to fix it on my end, just doing final touches and i'll publish it before going to bed.

@Ne-Ho Wait, how are you putting the chat as a widget? By default there's no chat widget:

@Ne-Ho Alright, taking a look now

@Ne-Ho I managed to fix this issue on my end, but for the global widget.
Can I see a pic of how the global widget looks?