-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 connect to key backup #26413
Labels
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Critical
Prevents work, causes data loss and/or has no workaround
T-Defect
Comments
weeman1337
added
T-Defect
S-Critical
Prevents work, causes data loss and/or has no workaround
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
Z-Labs
A-Element-R
Issues affecting the port of Element's crypto layer to Rust
labels
Oct 23, 2023
Legacy crypto behaves much the same way. In the console:
|
richvdh
removed
Z-Labs
A-Element-R
Issues affecting the port of Element's crypto layer to Rust
labels
Oct 24, 2023
richvdh
changed the title
Element-R: unable to connect to key backup
Unable to connect to key backup
Oct 24, 2023
The specific problem with this account is that the backup appears to have been signed with an old cross-signing key (and a device that no longer exists). |
We should create several issues for that:
See https://github.com/matrix-org/internal-config/issues/1315 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Critical
Prevents work, causes data loss and/or has no workaround
T-Defect
On one of my test accounts, this is shown in backup settings:
When I click "Connect to backup", I get:
But when I go back to settings, it is still the same as before.
In the console:
The text was updated successfully, but these errors were encountered: