From 7e547fead94f350ae8f8bef4f90bdcf82d29994f Mon Sep 17 00:00:00 2001 From: Bernhard B Date: Sat, 30 Jan 2021 21:49:38 +0100 Subject: [PATCH] Update TROUBLESHOOTING.md --- doc/TROUBLESHOOTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/TROUBLESHOOTING.md b/doc/TROUBLESHOOTING.md index f4aef0c..3737822 100644 --- a/doc/TROUBLESHOOTING.md +++ b/doc/TROUBLESHOOTING.md @@ -1,3 +1,8 @@ # The signal-cli-rest-api docker container won't start (signal_messenger_signal-cli-rest-api_1 exited with code 0) If your docker container stops with `signal_messenger_signal-cli-rest-api_1 exited with code 0`, make sure that the host port isn't already occupied by another process (see [here](https://github.com/bbernhard/signal-cli-rest-api/issues/2)). + +# Sending a message suceeds, but no message is sent + +According to [this](https://github.com/AsamK/signal-cli/issues/202) signal-cli ticket here, the receive endpoint needs to be called regularily. So, if sending a message seems to work, but no message is sent, please try to call the [Receive API endpoint](https://bbernhard.github.io/signal-cli-rest-api/#/Messages/get_v1_receive__number_). +