-
Notifications
You must be signed in to change notification settings - Fork 16
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
End2end encrypted mautrix-signal bridge fails with "Matrix connector: homeserver does not support appservice" #3206
Comments
Just found this information This is not good... |
MSC4190 should solve this. (But it is a relatively new MSC so might take some time until it is adopted) |
@xundeenergie The most recent versions of synapse and mautrix-signal should now work with MSC4190, mautrix-signal just needs to be configured to use it (and the appservice registration file needs to be updated). |
Do you mean the latest release of mautrix-signal (v0.7.4) or the latest nightly build? |
It should work in the latest release. |
and matrix-synapse I can not enable encryption for bridge... from mautrix-signal log: |
The whole log from mautrix-signal is
|
so... bridge is totally broken now. |
Describe the bug
A clear and concise description of what the bug is.
I setup a new mautrix-signal bridge with end2end-encryption. I configured double-puppeting. All according to the docs from mautrix-bridge.
I changed from matrix-synapse with directly configured oidc and ldap authentication to matrix-authentication-service successfully. After that, my mautrix-signal bridge stopped working... so i setup a new bridge to test it for this bugreport.
I asked in the matrix-room for the mautrix-signal bridge and got pointed to this issue:
spantaleev/matrix-docker-ansible-deploy#3493
The conclusion there is, that my problem is probably with matrix-authentication-service.
What i did:
Created an example-config from the mautrix-signal directly and filled in the neccessary information from an old bridge, which worked before migration to MAS.
I activated end2end-encryption and double puppetting.
When i start the bridge, i get this in the bridge-log and combined the nginx-log for synapse/matrix with tail to those 2 logfiles:
At the same time in homeserver.log: no entries!!
Deactivate e2e-encryption in bridge config and restart bridge
Now the bridge starts!!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A end2end-encrypted, double-puppeting mautrix-signal-bridge working with synapse an matrix-authentication-service.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: