-
-
Notifications
You must be signed in to change notification settings - Fork 299
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 register with signal-cli 0.13.1 #1491
Comments
I've the same two issues.
|
This persists in 0.13.3. |
CAPTCHA registration works for me on 0.13.3. Have you tried enclosing the captcha URI in single quotes? Perhaps there are some shell characters in the token. |
same issue with version 0.13.4 |
@orazioedoardo Enclosed in quotes or not, I get this issue, too, with master (0.13.5-SNAPSHOT). |
This persists in version 0.13.4 (I tried with a debian and a ubuntu). |
It worked for me today, after waiting a few days (perhaps it is a rate-limiting issue on Signal server's end and not a signal-cli -a +1XXXXXXXXXX -vv register --captcha signalcaptcha://signal-hcaptcha.[…]
signal-cli -a +1XXXXXXXXXX -vv verify XXXXXX
(phone numbers, full captcha, and verify code redacted) |
Logs of CAPTCHA registration, with signal-cli version 13.4.
Same with enclosed single quotes
|
I got reports from my users that they failed to register with "Error in registerWithCaptcha:Invalid captcha given."
I can reproduce this both using Dbus and directly from CLI.
Tried captchas from both sources given in the Wiki, immediately used "copy link" on the "Open Signal" URL which got me something like signalcaptcha://signal-hcaptcha-short.5fad97ac-7d06-4e44-b18a-b950b20148ff.registration.pYpZRKG_y9w2jtsiMglF9ODo
and used it with signal-cli (method SMS)
The number I'm trying to register is a German landline - so I was planning to use "voice" in a second step, but never get that far.
After several attemps I'm getting "Failed to register: StatusCode: 429 (RegistrationRetryException)" which is an indication that the server really got my registration attemps.
The text was updated successfully, but these errors were encountered: