Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Signature upload failure (no MSK found) when trying to cross-sign over federation
See original GitHub issueI tried to cross-sign @matthewtest:arasphere.net from @matthew:matrix.org from riot/web develop to riot/web develop. It failed with:
despite matthewtest having cross-signing set up:
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Signature upload failure (no MSK found) when trying to cross ...
It seems like this is actually the server deciding the other user doesn't have cross-signing keys after all, but the device doesn't recognise ......
Read more >16764: Drake e-Sign Online - Signature Troubleshooting
If the Status shows "Not sent," the documents were not successfully uploaded to the taxpayer's portal. The Signatures tab will also say "No...
Read more >AnyConnect VPN Client Troubleshooting Guide - Cisco
Introduction. This document describes a troubleshooting scenario which applies to applications that do not work through the Cisco AnyConnect VPN Client.
Read more >Verification, Updates, and Corrections - FSA Partner Connect
Because students sometimes make errors on their application, there is a process for verifying applications and making corrections.
Read more >ADFS 2.0 certificate error - Windows Server - Microsoft Learn
An error occurred during an attempt to build the certificate chain for the relying party trust signing certificate. Event ID 315
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed in synapse now
Update: one cause of this bug is now fixed, but there is another. I think 7252 would have affected anyone with existing accounts & rooms who added a device or cross-signing key, but I think 7276 will affect federated user IDs that no user on a server previously shared a room with (eg. if you crate two brand new accounts on different servers & try to verify them).