You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For someone who found the issue like I years later, this is not related to Signal Client, this is an issue of the protocol/servers that idk why blocked an account.
The solution is to call if you used Signal-cli
signal-cli -a $SENDER trust --trust-all-known-keys $RECIPIENT
The problem
Changed
trust_mode
via endpoint[POST] /v1/configuration/{number}/settings
(set "trust_mode": "always").Command:
curl -X POST -H "Content-Type: application/json" 'http://localhost:8080/v2/send' -d '{"message": "Test message", "number": "SENDER", "recipients": [ "RECIPIENT" ]}'
Response:
{"error":"Failed to send message due to untrusted identities"}
The
/v2/send
container log:Are you using the latest released version?
Have you read the troubleshooting page?
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
The text was updated successfully, but these errors were encountered: