-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 Bridge broken #3054
Comments
Tulir's git repo is not spantaleev's repo. The default value is
If you want to use the mainline version, I'd suspect that's where you would set it from. |
Hey! If you just change the docker tag, then your services are not correctly setup, here for instance it looks like systemd tries to start a python command for the go code... |
thanks a lot, different git repo makes sense. I tried setting it to
but it didnt work (same error as before) regarding the #3041: my problem was that I was logged out/thrown out automatically (couldnt figure out why till now) and now I can't log in again because of this |
This is due to the fact that the "latest" tag is not pointing anymore to a python code anymore (in both repos).
This issue is due to some changes Signal side and thus making the "old python" bridge unusable correctly... If you pull the latest master branch here you can update your bridge installation to the go code seamlessly -simply pull and run The only point is that you'll (or your users) need to re-link the devices. |
sorry, quite this late reaction: such great news - thanks a lot @pm-McFly for contributing and also for the extra info! |
As described here using
v0.4.3
(as used by the playbook) will not let new signal-bridge-users link a device.Upstream advice is to use main branch which would be
:latest
but when I putmatrix_mautrix_signal_version: latest
in my vars.yml (same as I put it directly in the.../defaults/main.yml
of the mautrix-signal-role) I get this error when starting thematrix-mautrix-signal.service
:docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "python3": executable file not found in $PATH: unknown.
I use arm64 with the latest system-, docker- and playbook updates.
The text was updated successfully, but these errors were encountered: