You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
MSC4190 should solve this. (But it is a relatively new MSC so might take some time until it is adopted)
I've creates a PR for mautrix/go for this. (This is used by the signal bridge)
Synapse has a draft PR for this MSC.
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: