signal-cli-rest-api/doc/TROUBLESHOOTING.md
2025-08-10 05:20:49 +02:00

1.4 KiB

Troubleshooting

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

Sending a message suceeds, but no message is sent

According to this 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.

Cannot send message to group - please first update your profile

If you get this message, it means that you first need to update your profile to set a name (and optionally an avatar).

Cannot send message - "User xxxxxxxxxx is not registered"

If you get this message, even after linking your Signal account, it could mean that the running container is starved of resources (memory/CPU) and executing its functions too slowly more details.