bbernhard / signal-cli-rest-api

Dockerized Signal Messenger REST API
https://bbernhard.github.io/signal-cli-rest-api/
MIT License
1.31k stars 155 forks source link

Can't get my number back into a signal group #515

Open markmghali opened 6 months ago

markmghali commented 6 months ago

I had to factory reset my phone. When I Setup signal on my phone again the my home group I use showed up right away. But none of the notifications from home assistant come through on my phone. My other member of the group gets there notifications from home assistant just fine. I looked at logs and tried resetting the group but couldn't figure it out.

Most likely my lack of knowledge.

Thank you

bbernhard commented 6 months ago

I guess it might be because your safety number changed (that happens when you factory reset your phone and install Signal again) and the Signal REST API doesn't trust the new safety number. You have to trust it manually with this endpoint: https://bbernhard.github.io/signal-cli-rest-api/#/Identities/put_v1_identities__number__trust__numberToTrust_

markmghali commented 5 months ago

I guess it might be because your safety number changed (that happens when you factory reset your phone and install Signal again) and the Signal REST API doesn't trust the new safety number. You have to trust it manually with this endpoint: https://bbernhard.github.io/signal-cli-rest-api/#/Identities/put_v1_identities__number__trust__numberToTrust_

hmm okay I tried running it and got this output. My cli syntax is also pretty bad so lots of trial and error.

running the docker on unraid

root@UNRAID:~# curl -X PUT -H "Content-Type: application/json" 'http://ip:port of docker/v1/identities/+number/trust/+number to trust'

{"error":"Couldn't process request - invalid request"}

guessing this is my lack of understanding. any help would be appreciated.

bbernhard commented 5 months ago

I guess it might be because your safety number changed (that happens when you factory reset your phone and install Signal again) and the Signal REST API doesn't trust the new safety number. You have to trust it manually with this endpoint: https://bbernhard.github.io/signal-cli-rest-api/#/Identities/put_v1_identities__number__trust__numberToTrust_

hmm okay I tried running it and got this output. My cli syntax is also pretty bad so lots of trial and error.

running the docker on unraid

root@UNRAID:~# curl -X PUT -H "Content-Type: application/json" 'http://ip:port of docker/v1/identities/+number/trust/+number to trust'

{"error":"Couldn't process request - invalid request"}

guessing this is my lack of understanding. any help would be appreciated.

Looks like you are missing the payload, see https://bbernhard.github.io/signal-cli-rest-api/#/Identities/put_v1_identities__number__trust__numberToTrust_.

In the end, it should look something like this:

curl -X 'PUT' \
  'http://<ip>:<port>/v1/identities/<number>/trust/<numberToTrust>' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "trust_all_known_keys": false,
  "verified_safety_number": "<safety number>"
}'

The safety number can be obtained via the corresponding GET request:

https://bbernhard.github.io/signal-cli-rest-api/#/Identities/get_v1_identities__number_

markmghali commented 5 months ago

Awesome Thank you! So Much!! I think I got it figured out now! Really appreciate the time

Getting the safety number and then adding it into your command worked! Thank you

markmghali commented 1 week ago

@bbernhard

Now I got another new phone trying to get my safety number. Using the same process and getting an error. I am running the docker in json-rpc mode.

Here is the output of the command. I know it's not much info:

root@RAID:~# curl -X GET -H "Content-Type: application/json" 'http://192.168.1.4:8777/v1/identities/+15153716197' 

{"error":"unexpected end of JSON input"}

most likely it is something wrong in my syntax? thank you again

bbernhard commented 6 days ago

Which version are you using? Does it work if you temporarily switch to the normal mode?

markmghali commented 6 days ago

I was originally in normal mode. And it said my number wasn't registered. I can try it again.

On Thu, Oct 3, 2024, 3:17 PM Bernhard B. @.***> wrote:

Which version are you using? Does it work if you temporarily switch to the normal mode?

— Reply to this email directly, view it on GitHub https://github.com/bbernhard/signal-cli-rest-api/issues/515#issuecomment-2392254966, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEENN4ERV4IW2WDCS5EK7FTZZWQ43AVCNFSM6AAAAABGCV6N3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSGI2TIOJWGY . You are receiving this because you modified the open/close state.Message ID: @.***>

markmghali commented 6 days ago

switched it to normal mode now and getting this error

# curl -X GET -H "Content-Type: application/json" 'http://192.168.1.4:8777/v1/identities/+15153716197' 
{"error":"User +15153716197 is not registered.\n"}#

running the docker on unraid

bbernhard commented 5 days ago

Which docker image version do you use?

markmghali commented 5 days ago

bbernhard/signal-cli-rest-api:latest

The Latest version 0.88

markmghali commented 2 days ago

Ok so I am in Native mode. on 0.89 I registered my number again got the safety number and tried this command again and getting an error


curl -X 'PUT' \
  'http://192.168.1.4:8777/v1/identities/+number/trust/+number_to_trust' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "trust_all_known_keys": false,
  "verified_safety_number": "safety_number"
}'

Here is the error:
{"error":"Failed to set the trust for this number, make sure the number and the fingerprint/safety number are correct.\n"