@crazycells said in Total vote count on topic list:
but this calculation makes more sense to us than the first post only.
And for me.
This topic was created as an entry in the Developer FAQ. Respond below if you have additional information to add re: SSO or other session-sharing implementations.
The common causes for a session mismatch error are usually one of the following:
config.json
fileIf 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.
cookieDomain
set in ACPSometimes admins set this value realising that they probably don't need to set it at all. The default is perfectly fine. If this is set, you'll want to revert the setting by editing your database directly:
Redis: hdel config cookieDomain
MongoDB: db.objects.update({ _key: "config" }, { $set: { "cookieDomain": "" } });
X-Forwarded-Proto
header from nginx/apacheIf you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure
property.
In nginx, you will need to add the directive like so:
location / {
...
proxy_set_header X-Forwarded-Proto $scheme;
...
}