Repository navigation
Replies: 1 comment
|
Well, that didn't take long. I restarted the docker container and I was able to send a message straight away. One weird bit of detail is that I had previously called the /v1/profiles/ endpoint and set the "name" value. I'm not sure if that caused some of the trouble but when I received the successful outbound message in the linux signal desktop app, it was in a new chat labeled with the "name" value and not in the chat with the phone number that was originally used to test inbound messages. Now, both chats are able to successfully send inbound messages that are being received by the same node red websocket connection. Best, |
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.
Wondering if anyone is wrestling with this one?
Submit challenge error: [428]
I've added the account in question as a second number to the docker instance. I have it connected to node red via a socket and I can see messages sent to this account as well as typing indicators, etc. I just can't send any messages due to "Failed to send message due to rate limiting." but every time I try to satisfy the challenge I'm getting the [428] response.
I'm also using the correct captcha url for challenges at https://signalcaptchas.org/challenge/generate and including the captcha string with the included "signalcaptcha://" prepend to the rest of the long string. I've also tried excluding this prepend but end up with the same [428] result.
Pulling what's left of my hair out.
Thanks for any suggestions.
Best,
Jeff
All reactions