Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending fails, requesting a Captcha #536

Open
2 tasks done
HorizonKane opened this issue May 15, 2024 · 2 comments
Open
2 tasks done

Sending fails, requesting a Captcha #536

HorizonKane opened this issue May 15, 2024 · 2 comments

Comments

@HorizonKane
Copy link

The problem

I installed the REST API addon succesful. I also managed to register with Captcha and got the activation key and activated.

I also added the necessary potion in the configuration.yaml.

When I create an automation to send a message, it fails with:

"Failed to send (some) messages: +49xxxxxxxxxx: CAPTCHA proof required for sending to "+49xxxxxxxxxx", available options "RECAPTCHA" with challenge token "91xx51ce-71dx1-4xx2-8xxb-f858xx54be3f", or wait "86400" seconds. To get the captcha token, go to https://signalcaptchas.org/challenge/generate.html After solving the captcha, right-click on the "Open Signal" link and copy the link. Use the following command to submit the captcha token: signal-cli submitRateLimitChallenge --challenge CHALLENGE_TOKEN --captcha CAPTCHA_TOKEN 17xx6899xxx2 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. Failed to send message due to rate limiting"

Tried normal, native and json-rpc mode.

Are you using the latest released version?

  • Yes

Have you read the troubleshooting page?

  • Yes

What type of installation are you running?

Home Assistant Signal Addon

In which mode are you using the docker container?

Normal Mode

What's the architecture of your host system?

x86-64

Additional information

No response

@bbernhard
Copy link
Owner

Please update your profile and set a username. This can be done with: https://bbernhard.github.io/signal-cli-rest-api/#/Profiles/put_v1_profiles__number_ (this should remove the warning about the unset username).

regarding the actual error: you are running into rate limiting issues (I guess you've sent too many messages in a short time). To lift the rate limiting restrictions use the challenge token that was returned in the error message together with this endpoint https://bbernhard.github.io/signal-cli-rest-api/#/Accounts/post_v1_accounts__number__rate_limit_challenge

@HorizonKane
Copy link
Author

Hi,

Will set the username.

And no, I did not send many message. In fact I just started the automation manually two or three times to send a single message which never worked :( Will try this anyways and post back later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants