Closed Hetti closed 2 years ago
We have introduced crayfish
as a new rust backend in order to use the upstream signal libraries in combination with the backend library from whisperfish, the signal client from sailfish. In order to find the root cause, did you compile crayfish? Second question is crayfish running an listening on 9081 when you start your client?
Ah well, I didn't compile crayfish and I'm not running it :)
anywhere some guide/doc for that?
Thanks! :+1:
Crayfish is an submodule in the cli and then you need cargo/rust installed, then it's in the makefile :) or cd crayfish&&cargo build
, also here is a hint: https://github.com/signal-golang/textsecure/tree/master/cmd/textsecure#installing
Thank you very much @nanu-c ! :smiley:
I got it running by building the crayfish binary in a docker container and copy it on the host into /usr/bin
on the system like described in the standalone signal-web-gateway doku for the signal binary itself :)
I have built the latest version https://github.com/signal-golang/textsecure/tree/v1.4.3 and wanted to run it in gateway mode like @morph027 documented it in https://morph027.gitlab.io/signal-web-gateway/
Unfortunately the crayfish does not work. When starting the program, following output is logged:
therefore it also unsuccessfully tries to connect to the crayfish server:
Any idea what I'm missing?
The service runs just as the low privileged signal user.