Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unable to decrypt message" eror when trying to read messages in an E2EE chat #28090

Open
dav9597 opened this issue Sep 23, 2024 · 2 comments
Open
Labels
A-E2EE S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@dav9597
Copy link

dav9597 commented Sep 23, 2024

Steps to reproduce

  1. Log in in your Element Account
  2. Open E2EE chat
  3. Not reading anything

Outcome

What did you expect?

reading messages

What happened instead?

"unable to decrypt" error every message

Operating system

Windows 10

Browser information

Firefox 130.0

URL for webapp

app.element.io

Application version

version Element: 1.11.77 Crypto version: Rust SDK 0.7.1 (c8c9d15), Vodozemac 0.6.0

Homeserver

No response

Will you send logs?

Yes

@dav9597
Copy link
Author

dav9597 commented Sep 23, 2024

probably this issue is referred to this one element-hq/element-meta#245

@dosubot dosubot bot added A-E2EE S-Critical Prevents work, causes data loss and/or has no workaround labels Sep 23, 2024
@strypey
Copy link

strypey commented Sep 23, 2024

I'm having this same issue. Using chat.iridescent.nz, the community-hosted Element-web app for matrix.iridescent.nz, I created a new session, and verified it from my Android session. I'm able to access all my rooms, but in all the encrypted rooms (including DMs), all previous messages say "unable to decrypt" (including my own).

It's not out of the question that there's some user error involved. But I've been using Matrix for about 5 years and I've tried everything I can think of, done some web searching, and followed various advice on joinmatrix.org etc. Nothing has worked so far.

When the problem last happened I was using LibreWolf 130.0-3, on Fedora 40 Mate-Compiz. Today I upgraded to LibreWolf 130.0.1-1, from the Fedora repos. If there's any more info I can supply to help you track down the bug, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants