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

Message cannot be decrypted, unable to decrypt attachment or message, Decryption issues, Unable to decrypt #24172

Closed
jittygitty opened this issue Jan 6, 2023 · 2 comments
Labels

Comments

@jittygitty
Copy link

jittygitty commented Jan 6, 2023

Steps to reproduce

I had posted this issue in Element Desktop about Decryption issues:
element-hq/element-desktop#500
But it was closed with reference that we should instead open such issues inside Element Web even if we're using desktop (since its same codebase I think).
(see element-hq/element-desktop#471 )

As a "follow-up" to the issue I initially posted at:
element-hq/element-desktop#500

Today I just had another Decryption issue, but this time in a channel with 3 people who were all registered/signed in on matrix.org and who were all using matrix.org server and not any custom homesever/dendrite etc. When I try to click a recent Text File Attachment upload, the .txt says its 163B , when i click on attachment link, i get a popup saying Error, Error decrypting attachment.

Element Desktop version is:
Element version: 1.10.10
Olm version: 3.2.8

Outcome

What did you expect?

I would expect no decryption errors.

What happened instead?

I got decryption errors.

Ctrl-Shift-I on Element Dekstop shows;
Uncaught (in promise) TypeError: Failed to fetch
at a.downloadSource (://vector/webapp/bundles/......./vendorsinit.js:2:384282)
......
rageshake.ts:72 Unable to decrypt attachment: TypeError: Failed to fetch
at a.downloadSource (://vector/webapp/bundles/.../vendors
init.js...)
at s.getFn ....
at s.get value [as value] .....
at i.decryptFile ...
at .... at Object.ze .....
at Ye ... at wr ...
e. @ rageshake.ts:72
rageshake.ts:72 Starting load of AsyncWrapper for modal

(It's difficult to correlate the console errors since I'm not familiar with it and don't see easy way to correlate specific error to its chat comment/post/attachment/etc)

Personally, I think that some of these errors could at least be easier to live with if we even had the OPTION to CACHE ALL LOCALLY as soon as it's received, because scrolling up through chat I notice now even Images that previously had worked, now have some small red triangle with exclamation mark, saying "Error decrypting image".

Currently if a server has any problems, you're locked out of your chat history. Now I realize this is a moot point for Element "WEB", but it isn't for Element "DESKTOP" or other client "apps". So for desktop app or other client apps, it would be nice to have option to LOCALLY SAVE all content. (Not sure if someone requested the feature already...)

Otherwise, yea, without such features, it's even more important that there be less of all these decryption issues.

Operating system

Windows 10

Browser information

No response

URL for webapp

No response

Application version

Element version: 1.10.10 Olm version: 3.2.8

Homeserver

matrix.org

Will you send logs?

No

@turt2live
Copy link
Member

I believe this issue will be related to the ongoing matrix.org outage - please track matrix-org/matrix.org#1601 for updates.

@turt2live turt2live closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2023
@richvdh
Copy link
Member

richvdh commented Sep 17, 2024

Duplicate of #28060

@richvdh richvdh marked this as a duplicate of #28060 Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants