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

Encryption upgrade fails to fetch keys from backup #13575

Open
tctovsli opened this issue May 7, 2020 · 11 comments
Open

Encryption upgrade fails to fetch keys from backup #13575

tctovsli opened this issue May 7, 2020 · 11 comments

Comments

@tctovsli
Copy link
Contributor

tctovsli commented May 7, 2020

Description

During first login on riot-web 1.16 (or subsequent "Restore keys from backup" or similar actions), the client fails to fetch keys from the server.
The GUI keeps spinning on "Fetching keys" and nothing happens.

Steps to reproduce

  • Log in with account that has key-backup enabled and member of some encrypted rooms before the new E2EE.
  • When prompted to upgrade encryption, enter the account password and press OK
  • The wheel spins and nothing happens. In the console of the browser this message is seen: restoreWithCachedKey failed: Error: "Couldn't get key" restoreKeyBackupWithCache https://riot.midlertidig.online/bundles/9f769ac7a648e2ec9507/vendors~init.js:2

Log: sent

Version information

  • Platform: web (in-browser)

For the web app:

  • Browser: Firefox 75.0
  • OS: Windows, Manjaro
  • URL: Private server, running riot-web version: v1.6.0
@tctovsli
Copy link
Contributor Author

tctovsli commented May 7, 2020

This also happens in the newest riot-desktop on Windows 10.

@dbkr
Copy link
Member

dbkr commented May 7, 2020

Trying to repro this but no luck so far. After enetering the account password and clicking, 'Next', you should get a prompt for your key backup passphrase. Are you not getting that prompt?

@tctovsli
Copy link
Contributor Author

tctovsli commented May 7, 2020 via email

@tctovsli
Copy link
Contributor Author

tctovsli commented May 7, 2020 via email

@DarwinAwardWinner
Copy link

I'm seeing this same on Mac OS, using an account on matrix.org. I get to this screen:

Screen Region 2020-05-07 at 16 29 15

After entering my password and pressing enter, I come to this screen:

Screen Region 2020-05-07 at 16 31 22

The spinner spins for a few seconds, and then I end up back at the same exact password entry screen as above, with no error message. I can enter my password again and the same thing will happen -- I just end up back where I started with no explicit indication of either progress or failure.

@DarwinAwardWinner
Copy link

Also, this might be a separate bug, but if I press "skip" and then "go back", I end up here, which is definitely not back where I was before:

Screen Region 2020-05-07 at 16 40 10

@poperigby
Copy link

I'm also seeing this on ArchLinux using a feneas.org account

@bergmannf
Copy link

bergmannf commented May 8, 2020

For me it was working when setting it up on the RiotX Android App, but once I try to set it up on the desktop application (Fedora using the Flatpak) it will go into a loop asking about the account passphrase.

It never asks about the key backup passphrase only the account password.

I also can't verify the session from my other device - after confirming it with the Emoji method it will say "The other party cancelled the verification."

When trying to use the website I can also see that the POST to https://matrix-client.matrix.org/_matrix/client/unstable/keys/device_signing/upload returns a 401 - Unauthorized.

@takiainen
Copy link

takiainen commented May 13, 2020

I've got this same issue, both with riot desktop (linux) and riot web at riot.im/staging. Cannot get in due to "encryption upgrade" failing over and over again. I also get following error message: "Unable to query secret storage status"

@pid42
Copy link

pid42 commented May 15, 2020

Same problem here, with Ubuntu 20.04 and Firefox 76.
It keeps asking the pasword to upgrade the encryption key, but does not accept the password.

@merrpink
Copy link

merrpink commented Jun 26, 2020

Same. Cannot verify new device and cannot read past messages. After clicking the little popup that asks if I want to verify new device on my original instance, and I click verify and verify again, spinner just spins and nothing happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants