-
Notifications
You must be signed in to change notification settings - Fork 10
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
mautrix signal does not bridge anymore #64
Comments
please provide the version of your bridge |
mautrix-signal 0.3.0+dev.unknown |
If it helps https://paste.yunohost.org/eqiyuluwoz |
This may be unrelated, but happened at the same time roughly 3 days ago. I am using a ASUS NUC server X86, latest yunohost release. The trigger for not being able to bridge anymore could be the recent upgrade of synapse to 1.69.0~ynh1 . The error message in the log talks about an SSL Handshake error. This is true for all Signal contacts. mausignald.errors.InternalError: org.whispersystems.signalservice.api.push.exceptions.PushNetworkException, javax.net.ssl.SSLHandshakeException, sun.security.validator.ValidatorException, sun.security.provider.certpath.SunCertPathBuilderException: org.whispersystems.signalservice.api.push.exceptions.PushNetworkException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target |
Should it be related to #59 ? |
I think it's related to https://gitlab.com/signald/signald/-/issues/343 |
possible workaround (not really tested) for those who are still under Yunohost 4 (debian 10), upgrade signald without upgrading mautrix_signal :
|
solved by #63 |
Describe the bug
A clear and concise description of what the bug is.
Context
Steps to reproduce
try to use mautrix_signal
Expected behavior
working bridge
Logs
The text was updated successfully, but these errors were encountered: