Fixed 🙂

I should have remembered that this database is from PROD, therefore, the cookie domain would need to be deleted. Issuing db.objects.update({_key: "config"}, {$set: {cookieDomain: ""}}); in the target DB under MongoDB, then restarting nodebb resolved the issue.

Able to login 🙂

Hello.

I know this was asked so much times on the forum, but I've actually a problem since I use the NodeJS build from Openshift. I saw everywhere that I had to change the nginx configuration file, but I don't how to achieve that with my current configuration.
I tried to install nginx, but it failed to resolve the issue.

So, I was thinking that someone found a fix or a way to edit nginx configuration with Openshift.

Thank you for your attention,
Best regards.

Thanks for the update @amarinelli

@Moritz-Friedrich said:

Weird enough, I just realized that at the old subdomain (as a CNAME) logging in is still possible...

Default this is not set to anything, so this doesn't need to be set... afaik

I figured out my issue...

MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

Re: gh#2424

julianlam created this issue in NodeBB/NodeBB closed Migrate CSRF system to send headers instead of in template values #2424