Repository navigation
Signal API with error sending signal messages to phone with Graphene OS running Molly #806
Unanswered
epradcliffe
asked this question in
Q&A
Replies: 1 comment
I guess when switching to the new client your safety number might have changed and now you need to trust the identity. (see https://bbernhard.github.io/signal-cli-rest-api/#/Identities/get_v1_identities__number_ and https://bbernhard.github.io/signal-cli-rest-api/#/Identities/put_v1_identities__number__trust__numberToTrust_ ) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have been using the signal rest api to send notifications from sonarr and radarr to my signal for a while now. I was not having any issues till I switched to the signal client Molly on my graphene phone. Sonarr and Radarr currently use the api to send notifications to my wife (who has regular android signal) and my phone using molly (and signal desktop.) The messages go through to my wife on the regular version of signal, but it fails to send to my number that uses Molly. The logs in the rest API show this.
"[GIN] 2026/03/06 - 04:53:09 | 201 | 4.399593648s | 172.20.0.1 | POST "/v2/send"
time="2026-03-06T04:53:09Z" level=info msg="INFO AccountHelper - The Signal protocol expects that incoming messages are regularly received."
time="2026-03-06T04:53:09Z" level=warning msg="WARN ManagerImpl - No profile name set. When sending a message it's recommended to set a profile name with the updateProfile command. This may become mandatory in the future."
Any ideas on how to get this working? My signal account works fine with all other uses. I just can't receive messages from the rest API.
Thanks!
All reactions