Summary Since upgrading to 3.9.0 we’re seeing a lot of “Invalid or expired session” errors which are filling the logs. Steps to reproduce Server 3.9.0, Chrome clients - otherwise conditions not very clear. Expected behavior Clean logs! I wouldn’t expect an error in the log under normal conditions. …

@jasonblais Just wanted to chime in here on an update. I upgraded version 4.0.2 to 4.1.0 and then today to version 4.2.0 I haven’t seen this behavior happen anymore, and I omitted the following from my Apache2 config: RequestHeader unset If-Modified-Since RequestHeader unset If-None-Match Everyt…

[image] jasonblais: @teatinker @vayenampudi @ionbasa Are any of you seeing the issue on our latest release, v4.1? @gubbins thanks for your note. Do you use a reverse proxy? If so, is it NGINX or Apache? For GitLab Auth, do you use GitLab omnibus? For GitLab Auth, did you follow our GitLab s…

@jasonblais I am currently unable to reproduce the looping issue. It’s possibly fixed. Unfortunately two things changed at once so I don’t know which it was, if either: some additional certificates were installed on the gitlab server to help with trust issues I added the “api” scope to the applica…

I’m still seeing this issue with with one user with Mattermost 4.1.0. I can reproduce it after clearing cache and in Chrome incognito mode. When I try to login with the affected user id, I see no log messages in the server log. I cannot say if this error started after session expiry. Since the user…

I spoke too soon - looking in the logs this morning I can see more examples of the log spamming from the refresh loop, so some users are still affected it seems.

Yeah, it sounds like similar to Gitlab SSO localization issue before which was fixed by setting currentLocale to en. Could you post the logs your seeing at Chrome console?

When trying to log in, I see this error five times in the chrome developer console: channel_utils.js:314 Uncaught (in promise) RangeError: Invalid language tag: at new Collator (native) at String.localeCompare (native) at o (http://chat.subshell.com/static/main.2b75939e681d6c1cdd03.js:…

Thanks @teatinker , could you post your Localization settings in config.json? Maybe something like this: "LocalizationSettings": { "DefaultServerLocale": "en", "DefaultClientLocale": "en", "AvailableLocales": "" }, for the user having issue, if you have access to datab…

"LocalizationSettings": { "DefaultServerLocale": "en", "DefaultClientLocale": "de", "AvailableLocales": "" }, sophora@chat:~/mattermost$ docker-compose exec mattermost bash root@d585f39a4bd6:/# l mattermost/i18n/ de.json en.json es.json fr.json it.json ja.json ko.json nl.json pl…

Yeah, it should not be empty. Better to have it set to de same as your DefaultClientLocale. Let us know if that solves the problem. I wonder how this user ended up with empty Locale. Was it created from usual user registration, bulk upload/import, switch from other auth service, or was changed only…

[Solved] Infinite refresh loop in browser clients, with "Invalid or expired session" log error spam

Troubleshooting

saturnino (Saturnino Abril) September 5, 2017, 11:03am 48

Could you post the logs and have it compared if still the same as to the original issue?

Topic		Replies	Views
Infinite refresh loop from clients Troubleshooting	26	6671	October 10, 2018
Infinite refresh loop in browser clients, with “Invalid or expired session” log error spam Troubleshooting	0	644	October 23, 2019
Users become logged in to another user Troubleshooting	17	4137	April 30, 2019
Mattermost 4.4.1 loses session and users disappear Troubleshooting	17	3833	November 23, 2017
User get logged out on every refresh Troubleshooting	21	2182	June 2, 2020

[Solved] Infinite refresh loop in browser clients, with "Invalid or expired session" log error spam

Related topics