Description
The problem
Recently I often get HTTP error 400 {“error”: “Specified account does not exist”}, after restarting docker everything returns to normal.
root@n305:~# curl -X POST -H "Content-Type: application/json" -d '{"logging": {"level": "debug"}, "message": "Hello World!", "number": "+4872xxxxxx", "recipients": ["+4869xxxxxx"]}' 'http://127.0.0.1:8488/v2/send' -w "%{http_code}" {"error":"Specified account does not exist"}400 root@n305:~# root@n305:~# curl -X POST -H "Content-Type: application/json" -d '{"logging": {"level": "debug"}, "message": "Hello World!", "number": "+4872xxxxxx", "recipients": ["+4869xxxxxx"]}' 'http://127.0.0.1:8488/v2/send' -w "%{http_code}" {"timestamp":"1744489180018"}201
Here is log from docker
signal-cli | [GIN] 2025/04/11 - 22:18:05 | 200 | 41.726µs | 172.26.0.1 | GET "/v1/about" signal-cli | [GIN] 2025/04/11 - 22:18:05 | 400 | 2.172654ms | 172.26.0.1 | POST "/v2/send" signal-cli | [GIN] 2025/04/12 - 20:16:50 | 200 | 37.597µs | 172.26.0.1 | GET "/v1/about" signal-cli | [GIN] 2025/04/12 - 20:16:50 | 400 | 1.196893ms | 172.26.0.1 | POST "/v2/send" signal-cli | [GIN] 2025/04/12 - 20:18:08 | 400 | 1.586918ms | 172.26.0.1 | POST "/v2/send" root@n305:/data/docker-ssd/signal-cli# docker compose down [+] Running 2/1 ✔ Container signal-cli Removed 0.1s ✔ Network signal-cli_default Removed 0.1s root@n305:/data/docker-ssd/signal-cli# docker compose up -d [+] Running 2/2 ✔ Network signal-cli_default Created 0.0s ✔ Container signal-cli Started root@n305:/data/docker-ssd/signal-cli# docker compose logs -f signal-cli | + set -e signal-cli | + [ -z /home/.local/share/signal-cli ] signal-cli | + usermod -u 1000 signal-api signal-cli | usermod: no changes signal-cli | + groupmod -o -g 1000 signal-api signal-cli | + chown 1000:1000 -R /home/.local/share/signal-cli signal-cli | + cat signal-cli | + cap_prefix=-cap_ signal-cli | + cat /proc/sys/kernel/cap_last_cap signal-cli | + seq -s ,-cap_ 0 40 signal-cli | + 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 | + [ json-rpc = json-rpc ] signal-cli | + /usr/bin/jsonrpc2-helper signal-cli | time="2025-04-12T20:19:32Z" level=info msg="Updated jsonrpc2.yml" signal-cli | + [ -n ] signal-cli | + service supervisor start signal-cli | Starting supervisor: supervisord. signal-cli | + supervisorctl start all signal-cli | + hostname -I signal-cli | + awk {print $1} signal-cli | + export HOST_IP=172.26.0.2 signal-cli | + 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 signal-cli | time="2025-04-12T20:19:33Z" level=info msg="Started Signal Messenger REST API"
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?
JSON-RPC Mode
What's the architecture of your host system?
x86-64
Additional information
No response