-
Hi all, I used an old version for some months. Some days ago, after upgrading to debian 11, I upgraded signal-cli to 11.4 and all worked fine. Even I surely did something wrong, I don't know what, and it doesn't work anymore... Here after the log with -vvv option when I try to do a receive, but it's the same for all commands. Thanks for your help. Rodolphe
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi, I just tried to do a fresh install of a VM debian 11. The install was the simplier as possible (just ssh server), then I only added openjdk-17-jre and install signal-cli => same result ... I also tried to remove all config files and try a register, same messages ... |
Beta Was this translation helpful? Give feedback.
-
OK, found the problem ! |
Beta Was this translation helpful? Give feedback.
OK, found the problem !
My "failtoban" is linked to suricata. It seems that I got somethings bad from "chat.signal.org" earlier that is required to communicate with signal services.
I just release the two IP associated with this hostname and it works well now... I have to understand what was understood as bad by Suricata 😅