Skip to content
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

Closed
whowantsmybigdata opened this issue Dec 21, 2023 · 5 comments
Closed

Mautrix-Signal Bridge broken #3054

whowantsmybigdata opened this issue Dec 21, 2023 · 5 comments
Labels
question This issue is a question related to installation

Comments

@whowantsmybigdata
Copy link

whowantsmybigdata commented Dec 21, 2023

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 put matrix_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 the matrix-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.

@ThellraAK
Copy link
Contributor

Tulir's git repo is not spantaleev's repo.

The default value is

matrix_mautrix_signal_docker_repo: "https://mau.dev/mautrix/signal.git"

If you want to use the mainline version, I'd suspect that's where you would set it from.

@pm-McFly
Copy link
Contributor

pm-McFly commented Dec 21, 2023

Hey!
Check this PR for updating to the go version of the bridge

#3041

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...

@whowantsmybigdata
Copy link
Author

whowantsmybigdata commented Dec 22, 2023

thanks a lot, different git repo makes sense.

I tried setting it to

matrix_mautrix_signal_docker_repo: "https://github.com/mautrix/signal.git"
matrix_mautrix_signal_docker_repo_version: "{{ 'main' if matrix_mautrix_signal_version == 'latest' else matrix_mautrix_signal_version }}"
matrix_mautrix_signal_docker_src_files_path: "{{ matrix_base_data_path }}/mautrix-signal/docker-src"

# renovate: datasource=docker depName=dock.mau.dev/mautrix/signal
matrix_mautrix_signal_version: latest
# renovate: datasource=docker depName=signald/signald
matrix_mautrix_signal_daemon_version: 0.23.2

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

@pm-McFly
Copy link
Contributor

pm-McFly commented Jan 3, 2024

thanks a lot, different git repo makes sense.

I tried setting it to

matrix_mautrix_signal_docker_repo: "https://github.com/mautrix/signal.git"
matrix_mautrix_signal_docker_repo_version: "{{ 'main' if matrix_mautrix_signal_version == 'latest' else matrix_mautrix_signal_version }}"
matrix_mautrix_signal_docker_src_files_path: "{{ matrix_base_data_path }}/mautrix-signal/docker-src"

# renovate: datasource=docker depName=dock.mau.dev/mautrix/signal
matrix_mautrix_signal_version: latest
# renovate: datasource=docker depName=signald/signald
matrix_mautrix_signal_daemon_version: 0.23.2

but it didnt work (same error as before)

This is due to the fact that the "latest" tag is not pointing anymore to a python code anymore (in both repos).
If you look to the service file in charge of starting the docker you'll see that it tries to fire-up a python command and therefore this is not present in the docker image.

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 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 just setup-all- everything will be kept.

The only point is that you'll (or your users) need to re-link the devices.

@whowantsmybigdata
Copy link
Author

sorry, quite this late reaction: such great news - thanks a lot @pm-McFly for contributing and also for the extra info!
The bridge works flawlessly again with no extra fiddling needed but the re-linking...

@luixxiul luixxiul added the question This issue is a question related to installation label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question related to installation
Projects
None yet
Development

No branches or pull requests

4 participants