Page 1 of 2

CAPCHA_NOT_READY

Posted: Sat May 05, 2018 8:56 am
by bitcoin

Code: Select all

Starting: 05/05/2018 10:49 AM
Validating: crypto2ico Proxy: <knip>
procauth: authorise.Process
Attempt login
Login: crypto2ico : password Proxy: <knip>
UA: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Login: get: https://apps.twitter.com/
Login: Get: https://twitter.com/login?redirect_after_login=https%3A//apps.twitter.com/
Login: Post: https://twitter.com/sessions 
Twitter locked account: 'To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.'
Attempt to unlock
Captcha ID = 1592163296
Waited: 8
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
* ERROR: An item with the same key has already been added.

Please go to the forum post for more help on authorising accounts: http://rootjazz.com/forum/viewtopic.php?f=30&t=1646
* UNKNOWN ERROR OCCURRED - see logs for more info.
If the problem continues, please submit logs to support.
An item with the same key has already been added.

Code: Select all

Starting: 05/05/2018 10:46 AM
Validate account  via login crypto2ico <email>
Login: crypto2ico : password Proxy: <knip> 
UA: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Login: get: https://apps.twitter.com/
Login: Get: https://twitter.com/login?redirect_after_login=https%3A//apps.twitter.com/
Login: Post: https://twitter.com/sessions 
Twitter locked account: 'To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.'
Attempt to unlock
Captcha ID = 1592148221
Waited: 6
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Validate account failed: An item with the same key has already been added.: crypto2ico
FAILED VERIFY: 

SUCCESS VERIFY: 

0 accounts validated out of 1
Started: 05/05/2018 10:46 AM
Finished: 05/05/2018 10:47 AM
ID: 1b989b38-fe67-478a-9763-fc3832f04ede
Action ran for: 0hr:1min:34s
Log ID: 11443

Re: CAPCHA_NOT_READY

Posted: Sat May 05, 2018 9:02 am
by bitcoin
Solution: probably: account didn't have a phone number yet. Add a phone number that Twitter doesn't know yet.

Re: CAPCHA_NOT_READY

Posted: Tue May 08, 2018 8:04 am
by support@rootjazz
bitcoin wrote: Sat May 05, 2018 8:56 am

Code: Select all

Starting: 05/05/2018 10:49 AM
Validating: crypto2ico Proxy: <knip>
procauth: authorise.Process
Attempt login
Login: crypto2ico : password Proxy: <knip>
UA: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Login: get: https://apps.twitter.com/
Login: Get: https://twitter.com/login?redirect_after_login=https%3A//apps.twitter.com/
Login: Post: https://twitter.com/sessions 
Twitter locked account: 'To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.'
Attempt to unlock
Captcha ID = 1592163296
Waited: 8
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
* ERROR: An item with the same key has already been added.

Please go to the forum post for more help on authorising accounts: http://rootjazz.com/forum/viewtopic.php?f=30&t=1646
* UNKNOWN ERROR OCCURRED - see logs for more info.
If the problem continues, please submit logs to support.
An item with the same key has already been added.

Code: Select all

Starting: 05/05/2018 10:46 AM
Validate account  via login crypto2ico <email>
Login: crypto2ico : password Proxy: <knip> 
UA: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Login: get: https://apps.twitter.com/
Login: Get: https://twitter.com/login?redirect_after_login=https%3A//apps.twitter.com/
Login: Post: https://twitter.com/sessions 
Twitter locked account: 'To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.'
Attempt to unlock
Captcha ID = 1592148221
Waited: 6
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 4
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Not solved yet: waiting: 
CAPCHA_NOT_READY
Waited: 5
Validate account failed: An item with the same key has already been added.: crypto2ico
FAILED VERIFY: 

SUCCESS VERIFY: 

0 accounts validated out of 1
Started: 05/05/2018 10:46 AM
Finished: 05/05/2018 10:47 AM
ID: 1b989b38-fe67-478a-9763-fc3832f04ede
Action ran for: 0hr:1min:34s
Log ID: 11443
Thanks for the detailed log. Always appreciated.
Solution: probably: account didn't have a phone number yet. Add a phone number that Twitter doesn't know yet.
Not sure if this is a solution.
I think martin should watch the log as the log has some incomplete response.
I have reported the log number to martin and he will investigate it and reply back here.
Perhaps, he might ask for accounts having hit by captcha.



Best regards

Re: CAPCHA_NOT_READY

Posted: Wed May 09, 2018 12:03 am
by martin@rootjazz
Hi, I hope you are well.

Downloading logs now.

Re: CAPCHA_NOT_READY

Posted: Wed May 09, 2018 12:23 am
by martin@rootjazz

Code: Select all

403 Forbidden: The server understood the request, but is refusing to fulfill it.
I see this in the logs, not sure if related to the issue though


Actually it might be related, it appears the account has hit a recaptcha checkpoint which is currently not supported as they are doing something sneaky with JS redirects that I haven't been able to solve yet.

The code is half in, and it is that which is failing although not sure why...


I'll get an update out to handle this and better log out what is happening



Regards,
Martin

Re: CAPCHA_NOT_READY

Posted: Wed May 09, 2018 7:36 pm
by bitcoin
martin@rootjazz wrote: Wed May 09, 2018 12:03 am Hi, I hope you are well.

Downloading logs now.
I wish the same for you :)

I haven't tested yet by adding a mobile number. I couldn't unlock it online either without that mobile number. I need to buy a new number for that, haven't gotten around doing it - it's not a big account of mine.

Will let you know if I encounter more problems when all is updated on my end.

Re: CAPCHA_NOT_READY

Posted: Thu May 10, 2018 4:49 am
by support@rootjazz
bitcoin wrote: Wed May 09, 2018 7:36 pm
martin@rootjazz wrote: Wed May 09, 2018 12:03 am Hi, I hope you are well.

Downloading logs now.
I wish the same for you :)

I haven't tested yet by adding a mobile number. I couldn't unlock it online either without that mobile number. I need to buy a new number for that, haven't gotten around doing it - it's not a big account of mine.

Will let you know if I encounter more problems when all is updated on my end.

:)

Re: CAPCHA_NOT_READY

Posted: Fri May 11, 2018 1:50 am
by martin@rootjazz
bitcoin wrote: Wed May 09, 2018 7:36 pm
martin@rootjazz wrote: Wed May 09, 2018 12:03 am Hi, I hope you are well.

Downloading logs now.
I wish the same for you :)

I haven't tested yet by adding a mobile number. I couldn't unlock it online either without that mobile number. I need to buy a new number for that, haven't gotten around doing it - it's not a big account of mine.

Will let you know if I encounter more problems when all is updated on my end.
I am fairly sure it is the recaptcha. The logs showed you were returned a response URL which meant captcha. The program started to process it (my half left in code) then bombed out as the half code wasn't finished and shouldn't be there.

The update coming is delayed as got some low level changes to how the GUI handles accounts and caching to make things a bit quicker less RAM intensive, just need to get that tested off and will push the new build

Re: CAPCHA_NOT_READY

Posted: Fri May 18, 2018 9:38 am
by bitcoin
no problem - still have to get myself a new mobile number.

Re: CAPCHA_NOT_READY

Posted: Sat May 19, 2018 3:23 pm
by martin@rootjazz
bitcoin wrote: Fri May 18, 2018 9:38 am no problem - still have to get myself a new mobile number.
could be worse, I need to get a new phone as my daughter wanted to see how well my phone would bounce down the stairs. Unfortunately it did not really bounce, more of a smash smash smash smash all the way down lol