-
-
Notifications
You must be signed in to change notification settings - Fork 317
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 Android phone : Getting Request verify error: Bad response: 402 Payment Required #201
Comments
I am also having this issue no matter where I register the number |
Same situation |
I had the same issue when I requested registration using IP from different country than mobile phone. It worked when registered from same. |
I requested registration using an IP address in the same country as the mobile phone. It didn't work. |
Same Same...
|
I live in french and my server is in french but i have the same problem Request verify error: Bad response: 402 Payment Required |
Do you have one solution ? |
Can you register with that number on the official signal clients? |
Yes ... but not with signal-cli... Edit: I refresh my installation and its WORK thank'you |
fixed in recent signal-cli versions, that support captchas for registration if required. |
Hello,
I have downloaded and untarred signal-0.6.2 to /usr/local/bin/ on Debian 8.11 as per the instructions. I have also installed haveged and my java version is 1.7.0_201.
My server is based in the UK, so is the Android phone I am trying to register and (not that it matters for my current purposes) so am I.
However, when i try to register my phone, I get this :
./signal-cli -u +44123456789 register
Request verify error: Bad response: 402 Payment Required
I have searched for this issue and can't find any reference to it.
Please let me know what other information I need to provide and any and all help greatly appreciated. For reference, I am trying to use signal-cli on my xymon server so that I can get admin alerts on my smartphone.
Thank you.
Kind Regards.
The text was updated successfully, but these errors were encountered: