-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Submit challenge error: [413] Rate limit exceeded: 413 #1497
Comments
Possible ... a verbose log with There are two different captcha pages, the one for "challenge" should be used: https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha#get-captcha-token |
I have already learned the hard way that the CAPTCHA must be submitted from the same IP from which it is solved. My submitRateLimit request today succeeded as expected. Closing this until I can reproduce again. |
excerpt from submitRateLimit invocation with verbose logs
|
It looks like this might be the expected behavior - two solves per 12 hours, after which attempts to solve will be... ratelimited. |
I have the same problem. |
@johe123qwe the only solution I've found is to wait out the timeout. |
Trying to clear a ratelimit with the submitRateLimit command, and apparently the submitRateLimit command itself can be ratelimited?
Any ideas what might be going on here? Weird times.
....
WARN ServiceConfig - activated HTTP logging
Submit challenge error: [413] Rate limit exceeded: 413
The text was updated successfully, but these errors were encountered: