-
Notifications
You must be signed in to change notification settings - Fork 83
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
SignatureVerifyException on Unbind threepids #512
Comments
Could we have the full traceback and any nearby logs please? Can you also please confirm which version of Sydent you're running? |
How do I get a traceback? There's no error thrown, I tracked the I'm on version 2.5.1 Sydent Logs:
Synapse Logs:
|
Hi! Is your homeserver using the Is it possible for you to share your server name so I can have a look around? It's quite hard to diagnose without it. Thanks |
Yeah, hit me up at @w5d33xzsy9m7vn6v:matrix.org and we can go from there. |
In our dm, I ran reivilibre's custom branch
reivilibre's conclusion was this:
|
I'm not sure if it's the case here, but a common cause for failure to validate the signature on federation requests is an incorrect reverse-proxy setup - in particular, including a path after the host:port in a |
I've verified I don't have the slash after the host:port on any of my nginx configs. Just to give you all the info, here's my proxy setup:
I've been suspicious this problem has something to do reverse proxies. Would you like me to share all my nginx configs so you can verify they're all correct? |
If you don't mind sharing your nginx configuration, then I'd be happy to check for any obvious problems. However, I suspect I see the problem now. In your synapse log snippet:
... which is to say that Synapse thinks it is connecting to a server called
... note in particular, The mismatch will cause the signature verification to fail. In other words, you need to decide if your identity server is called |
Using the payloads and verification keys you sent me in DM, this above is indeed the problem. The signature verification works if (Will close since I think this is resolved; if it still doesn't work after that then the issue can be reopened) |
I see that I indeed set |
We'd welcome pull requests improving the documentation (though this is far from the only problem - see #101) |
I'm unable to remove my threepid email address from my identity server. Sydent throws SignatureVerifyException in
/sydent/hs_federation/verifier.py
atsignedjson.sign.verify_signed_json()
I run my homeserver on
matrix.example.com
and have both SRV records and the following in my nginx config to make the accounts show up asexample.com
. federationtester.matrix.org says my server passes all tests. I don't have port 8448 open.This is a signing error but everything works up until the
signedjson.sign.verify_signed_json()
. The federation tester says all parts of the signed message are valid and I can join federated servers and others can join my federated rooms/spaces.Everything else is working as it should so I really don't know what else to do here.
The text was updated successfully, but these errors were encountered: