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

cannot complete rate-limit challenge #638

Open
2 tasks done
kevincw01 opened this issue Jan 1, 2025 · 2 comments
Open
2 tasks done

cannot complete rate-limit challenge #638

kevincw01 opened this issue Jan 1, 2025 · 2 comments

Comments

@kevincw01
Copy link

kevincw01 commented Jan 1, 2025

The problem

After successfully registering, completing the initial captcha and doing sms verification, when I try to send a message I always receive the rate-limit error message. So I do the rate limit api but it always gets the message: {"error":"Submit challenge error: [400] Bad response: 400 : {\"code\":400,\"message\":\"invalid captcha action\"}"}. I have tried with a new account and spaced it over multiple days but it always fails here. I am following the rate-limit api per below:

` curl -X 'POST'
'http://localhost:8080/v1/accounts/%2BREDACTED/rate-limit-challenge'
-H 'accept: application/json'
-H 'Content-Type: application/json'
-d '{
"captcha": "signalcaptcha://signal-hcaptcha.5fad97ac-7d06-4e44-b18a-b950b20148ff.registration.P1_eyJ0eSNIPPED",
"challenge_token": "ae19341a-839a-4b9a-9019-863775ae2630"
}'

any tips to successfully get through this step? I can successfully receive messages, just can never send.

Are you using the latest released version?

  • Yes

Have you read the troubleshooting page?

  • Yes

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

@bbernhard
Copy link
Owner

Please give this version a try: bbernhard/signal-cli-rest-api:0.175-dev

In case it doesn't work, please try switching to the normal/native mode and give it another try.

@cdpb
Copy link

cdpb commented Jan 12, 2025

@bbernhard 0.175-dev worked for me, thanks

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

3 participants