The common causes for a session mismatch error are usually one of the following:
1. Mis-configured URL parameter in your config.json file
If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.
2. Improper/malformed cookieDomain set in ACP
Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:
If this is set, you'll want to revert the setting by editing your database directly:
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.
I must have misconfigured something. But I cannot find out what the problem is. Is anone else experiencing lots of "upstream prematurely closed connection while reading response header from upstream" errors in their nginx log?
Tried tweaking buffers sizes etc but I see no difference. Get the feeling that nodebb is terminating polling clients connections.