element-hq / element-hq/element-web

I have to use the recovery key everytime I turn my laptop off and on again

Open
#32,472 1 comment 0 reactions 0 assignees View on GitHub
A-E2EE A-Electron A-Session-Mgmt O-Frequent S-Critical T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Where are you starting? What can you see?
-I start Element and it kicks me out of my login, this window pops up:

Image
translation:
Session restore failed.
We encountered a problem restoring your previous session. If you were previously using a more recent version of Element, your session might be incompatible with that version. Please close this window and revert to the more recent version. Clearing your browser cache may resolve the issue, but it will log you out and render encrypted messages unreadable.

Click: Clear browser cache and log out - submit log files

3. What do you click?
Clear browser cache and log out, then I log back in

5. More steps…
Submitting the log files through the settings tab

Side note:
I never did anything different, it was working fine, then I was on vacation for 1-2 weeks and when I came back to work again teh problem suddenly appeared. I tried changing the Element version from 1.12.8 to 1.12.9, but it didn't fix it.

### Outcome

#### What did you expect?
Element opens normally without needing to recover.
It's really annoying because I can't see any messages anymore after clearing the cache every single time.

#### What happened instead?
Element kicked me out of my login and wants me to recover.

### Operating system

Ubuntu

### Application version

Version von Element: 1.12.9 Krypto-Version: Rust SDK 0.16.0 (95b5e83), Vodozemac 0.9.0

### How did you install the app?

From the website

### Homeserver

local server, matrix, idk the version

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.