element-hq
Element chat keeps logging out
Steps to reproduce
My element chat is logging out every 30-60 minutes. 5-10 times per day. I have re-installed the laptop this week, cleaned chrome history, ran ClamXAV. Seems there might be an internal error in element messeging app for this melfunction to repeatedly occur.1. Where are you starting? What can you see? 2. What do you click? 3. More steps…
Outcome
Problem isn't solved
Operating system
macOS
Browser information
Chrome
URL for webapp
No response
Application version
No response
Homeserver
No response
Will you send logs?
Yes
Hi Will, Hi Michael,
I don't understand what logs and ragshake commands are. Trigger the defect
- I don't know how to do it. Submit anonymous logs to developers - I don't know how to do it.
[image: 352048928-a2c7d629-7ddb-41c6-94e7-be6f84181ef9.png]
Tomi
Am Do., 25. Juli 2024 um 10:21 Uhr schrieb Michael Telatynski < @.***>:
They are in the issue template which they filled
image.png (view on web) https://github.com/user-attachments/assets/a2c7d629-7ddb-41c6-94e7-be6f84181ef9
— Reply to this email directly, view it on GitHub https://github.com/element-hq/element-web/issues/27810#issuecomment-2249872880, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIB6FWZ33RUTYKMEESAKG7DZOC7QXAVCNFSM6AAAAABLMCYFQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZHA3TEOBYGA . You are receiving this because you authored the thread.Message ID: @.***>
Hi Will, Hi Michael, I don't understand what logs and ragshake commands are. Trigger the defect - I don't know how to do it. Submit anonymous logs to developers - I don't know how to do it. [image: 352048928-a2c7d629-7ddb-41c6-94e7-be6f84181ef9.png] Tomi Am Do., 25. Juli 2024 um 10:21 Uhr schrieb Michael Telatynski < @.>: … They are in the issue template which they filled image.png (view on web) https://github.com/user-attachments/assets/a2c7d629-7ddb-41c6-94e7-be6f84181ef9 — Reply to this email directly, view it on GitHub <#27810 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIB6FWZ33RUTYKMEESAKG7DZOC7QXAVCNFSM6AAAAABLMCYFQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZHA3TEOBYGA . You are receiving this because you authored the thread.Message ID: @.>
Have you tried typing /rageshake and sending that in Element Web?
Sorry. I don't understand. Typing /rageshake? Where? Element Web? What is Element Web? Element chat or?
Forgive me for my technical illiteracy. I don't understand any of the terminology nor do I understand the process of submitting this error.
Sorry. I don't understand. Typing /rageshake? Where? Element Web? What is Element Web? Element chat or?
Forgive me for my technical illiteracy. I don't understand any of the terminology nor do I understand the process of submitting this error.
The desktop app 'Element', which I think you're referring to as Element Chat, is what we call Element Web.
In any conversation within Element Web you can type commands that start with /, that have special functions.
One of those is /rageshake which will send logs to the Element Web team.
So if you can, please try typing /rageshake myproblem into any conversation in Element Web (for example in a direct message with somebody or a group chat, it doesn't matter) and hit enter. Like in the screenshot above.
EDIT: Looks like someone has done this on your behalf, yesterday.
I have submitted the debug log this week with Lewis. I have addressed this issue weeks ago. I am now pending in this labyrinth of Github and Element web debug logs for too long. I am disappointed with the process.
Looks like token expires so either token refresh is not working or we are hitting the idempotency bug in MAS. Logs are missing detail on that
Similar problem here, Elemenet Web is logged out (session still exists, but it's forgotten by Element Web) typicaly overnight from my self hosted Element Web/Synapse/MAS instance. However MAS is still logged in. I've used upstream OIDC Authentik without resfresh tokens so far. No such problems spotted on Element X Android so far. Will post console logs from Element Web (1.11.92) when it happens next time. On the other hand this issue doesn't occur on beta.element.io web using password.
There is the log. I can remember that I've seen that message M_UNKNOWN_TOKEN also on Element X, however Element X survived that issue and session wasn't logged out.
console-export-2025-2-24_11-52-24.txt
It happened again after it worked fine few days back. Not sure if it's the same reason, now it seems to be caused by new version avaiable...
console-export-2025-2-27_18-51-28.txt