Infos:
- Used Zammad version: 6.4.1
- Used Zammad installation type: Self Hosted
- Operating system: Ubunbtu server
- Browser + version: Chome, Firefox, …
Expected behavior: Open session in multiple tabs/ loggin simultaneously
Actual behavior:
- Only 1 tab, if I open new one, says that the other is going to close
Steps to reproduce the behavior:
- Open session in different tabs or navigator
Hello everyone,
I am experiencing an issue with my Zammad instance: whenever I open a new tab (or window) with the same user account, the active session closes and I receive the following message:
"A new session has been created with your account. This session will be terminated to avoid a conflict."
So far, I have performed the following checks:
single_session_mode:
Running Setting.get('single_session_mode') in the Rails console returns nil, and attempting to set it with Setting.set('single_session_mode', false) indicates that this parameter does not exist. This rules out that a single-session mode is active.
session_timeout:
The value obtained is 2419200 (28 days), which means that the session is not being closed due to inactivity.
Domain and HTTPS:
I access Zammad via a domain with HTTPS, so it does not seem to be an issue related to cookies being misconfigured by using only an IP or HTTP.
Testing in Various Browsers:
The issue occurs in Chrome, Firefox, and Edge, even in incognito mode and with all extensions disabled.
Zammad Logs:
I have monitored the production.log while replicating the issue, and no messages indicate session invalidation or the creation of a new session—only normal requests and routine process messages (e.g., "Generate 'Session' data." or "Channel.fetch").
I would appreciate any guidance or suggestions on how to pinpoint the cause of this behavior. Could it be related to some proxy configuration or an issue with how cookies are handled by the browser?
Thank you in advance for your help.
Regards,