Error 400 when sending to a group number

[r3mi]

The problem

Hello,
since Tuesday (26th May) I am unable to send to a group number.
signal-cli-rest-api was running fine, no change on my side, but now I get a long delay when sending to group then error 400.

curl -X 'POST' \
  'https://signal-api.<redacted>/v2/send' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "message": "hello world",
  "number": "+<redacted>",
  "recipients": [
    "group.OG<redacted>z0="
  ]
}'

docker logs in debug mode

time=2026-05-28T20:41:24Z
level=debug
msg=If you want to run this command manually, run the following steps on your host system:
time=2026-05-28T20:41:24Z
level=debug
msg=*) docker exec -it f6d44e3eb5d9 /bin/bash
time=2026-05-28T20:41:24Z
level=debug
msg=*) su signal-api
time=2026-05-28T20:41:24Z
level=debug
msg=*) echo 'hello world' | signal-cli-native --config /home/.local/share/signal-cli -a +<redacted> send --message-from-stdin -g 8n<redacted>Ws= --notify-self
[GIN] 2026/05/28 - 20:43:24 | 400 |          2m0s |  100.93.207.124 | POST     "/v2/send"

(so a 2 min delay before the 400)

{
  "error": "process killed as timeout reached"
}

Are you using the latest released version?

• Yes

Have you read the troubleshooting page?

• Yes

What type of installation are you running?

signal-cli-rest-api Docker Container

In which mode are you using the docker container?

Native Mode

What's the architecture of your host system?

x86-64

Additional information

Not sure how or if it is related to #851 ?

thanks for signal-cli-rest-api !

[r3mi]

Reverting to 0.98 fixes my issue: group sending works ok again.
What is strange is that I was using 0.99 since May 2nd, and it was working ok so far.

[bbernhard]

does it also happen with bbernhard/signal-cli-rest-api:1779833895-ci?

[r3mi]

thanks for the quick reply!
unfortunately with bbernhard/signal-cli-rest-api:1779833895-ci I now get errors on all my tests e.g. 500 for "/v1/accounts", and 400 for "/v2/send", be it phone numbers or group numbers.
Do I need to change some configuration to use that image ?
Currently: using mode native, and running in docker rootless (since always -- not sure to understand what the new rootless image will be bringing ?)

[bbernhard]

What specific error do you get now with the new image? Please also try to enable the debug mode (https://github.com/bbernhard/signal-cli-rest-api/blob/master/doc/DEBUG.md) and try the command directly within the container.

[r3mi]

with debug

+ set -e
+ [ -z /home/.local/share/signal-cli ]
+ usermod -u 1000 signal-api
usermod: no changes
+ groupmod -o -g 1000 signal-api
Changing ownership of /home/.local/share/signal-cli to 1000:1000
+ [ true != false ]
+ echo Changing ownership of /home/.local/share/signal-cli to 1000:1000
+ chown 1000:1000 -R /home/.local/share/signal-cli
+ cat
+ cap_prefix=-cap_
+ cat /proc/sys/kernel/cap_last_cap
+ seq -s ,-cap_ 0 40
+ caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40
+ [ native = json-rpc ]
+ [ native = json-rpc-native ]
+ hostname -I
+ awk {print $1}
+ export HOST_IP=<redacted>
+ exec setpriv --reuid=1000 --regid=1000 --init-groups --inh-caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40 signal-cli-rest-api -signal-cli-config=/home/.local/share/signal-cli
time=2026-05-28T21:44:36Z
level=info
msg=Started Signal Messenger REST API
time=2026-05-28T21:44:49Z
level=debug
msg=If you want to run this command manually, run the following steps on your host system:
time=2026-05-28T21:44:49Z
level=debug
msg=*) docker exec -it 23a4a3fc5d6c /bin/bash
time=2026-05-28T21:44:49Z
level=debug
msg=*) su signal-api
time=2026-05-28T21:44:49Z
level=debug
msg=*) echo 'hello world' | signal-cli-native --config /home/.local/share/signal-cli -a +<redacted> send --message-from-stdin -g 8n<redacted>Ws= --notify-self
[GIN] 2026/05/28 - 21:44:49 | 400 |     402.098µs |  100.93.207.124 | POST     "/v2/send"

and response body

{
  "error": "exec: \"signal-cli-native\": executable file not found in $PATH"
}

in the container: after chmod +x /opt/signal-cli-0.14.4.1/bin/signal-cli-native (was 0644):
my tests are now OK !
(including phone send + group send)

[bbernhard]

Aaah...looks like a broke something with the recent refactoring. Thanks a lot for letting me know! I'll fix it right away

[bbernhard]

Should be fixed with bbernhard/signal-cli-rest-api:1780010737-ci

[r3mi]

Should be fixed with bbernhard/signal-cli-rest-api:1780010737-ci

I confirm it works ok for me.
thanks!