This repository has been archived by the owner on Mar 7, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 520
Cannot create new wallet - ("Wrong Captcha") bug? Please resolve.. its been over a month now #570
Comments
do you get to the new window which asks for new password |
man. Fuck blockchain!!!!!!!!! It’s unfortunately a bad player, witch will
be gone sooner than later I truly hope
14. mar. 2022 kl. 18:17 skrev JustJackkie ***@***.***>:
… I get this error when I try to create new wallet using api/v2/create
({"success":false,"message":"Wrong captcha"}).
Everything was working before then it just randomly started giving me this
error out of nowhere. I am running node service and sending my requests to
it - Service v0.26.3, Node v6.4.0
I have tried contacting blockchain regarding this issue for over a month
now without a response.
Does anyone know how to resolve this?
—
Reply to this email directly, view it on GitHub
<#570>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGFY6JFXAVQS2R7BKIVYRTU75YBLANCNFSM5QWGGW3A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I tell you!! Get as fast as you can out, and never look back |
hi, how did you get Api key? i tried many times but nobody replied me. |
@aris2dev |
No, i created success request but nobody replied me yet about API. |
@isieditors can you please explain how to solve this? Thanks |
@mprenditore |
Wait till you tried a year!! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I get this error when I try to create new wallet using api/v2/create ({"success":false,"message":"Wrong captcha"}).
Everything was working before then it just randomly started giving me this error out of nowhere. I am running node service and sending my requests to it - Service v0.26.3, Node v6.4.0
I have tried contacting blockchain regarding this issue for over a month now without a response.
Does anyone know how to resolve this?
The text was updated successfully, but these errors were encountered: