Closed rianbk closed 1 year ago
Is this consistent? Does this happen in every attempt? Please be aware that no matter how great the 2captcha service is, it is still actual people solving your captcha and the error rate is not negligible. I have had times with 3 concecutive failures. If this is actually consistent I will try to block some time next week to have a look at it. Please provide feedback so I know.
Hi, yes. I have never successfully got it to work.
Hi @rianbk , I have spent the last hour trying out the code and I cannot recreate the issue. Could you please try out the code without the captcha2 solver (it will use an interactive one, if you are on iterm you will get the picture and you can solve yourself, if not you will get a link that you can follow and solve) and let me now if that still fails for you?
Hi @rianbk , have you tried without the 2captha solver?
Hey @costastf, sorry for the late reply. I've been traveling. I've done some more testing.
I created a new account to test against, and everything works fine. Going back to my older account, i'm now getting the error "Unable to resolve the account"
Hi @rianbk , a stack trace would help troubleshooting, if you want to look into this any further. It seems that something is off with your account and it might be interesting to see if we can figure out what.
Hey @costastf, happy to help just let me know exactly what you need.
Traceback (most recent call last):
File "/Users/***/code/play/test.py", line 11, in <module>
print(account_manager.iam.billing_console_access)
File "/Users/***/code/play/venv/lib/python3.10/site-packages/awsapilib/console/console.py", line 752, in iam
session = self._get_billing_session(self.email,
File "/Users/***/code/play/venv/lib/python3.10/site-packages/awsapilib/console/console.py", line 559, in _get_billing_session
redirect_url = self._get_root_console_redirect(email, password, session, mfa_serial=mfa_serial)
File "/Users/***/code/play/venv/lib/python3.10/site-packages/awsapilib/console/console.py", line 517, in _get_root_console_redirect
raise UnableToResolveAccount(f'Unable to resolve the account, response received: {response.text} '
awsapilib.console.consoleexceptions.UnableToResolveAccount: Unable to resolve the account, response received: {"state":"FAIL","properties":{"CES":"***","Captcha":"true","CaptchaURL":"***","email":"***@***.com","captchaObfuscationToken":"{\"b64KeyCipherData\":\"***"}"}} with status code: 200
Let me know if i obfuscated something you need, just not sure whats sensitive or not. Let me know if you need more
It seems that you are not getting a captchaStatusToken
as expected. I would like to try out the worklflow until the password usage. Do you use keybase or something like that that you could share with me securely the email of the account so I can try it out?
@costastf I've messaged you on keybase
We are facing the same problem. Within the last 6 weeks we had 400+ auth errors. All of them looking like this:
awsapilib.console.consoleexceptions.InvalidAuthentication: Unable to authenticate, response received was: {"state":"FAIL","properties":{"CES":"...","Captcha":"true","CaptchaURL":"https://opfcaptcha-prod.s3.amazonaws.com/3485cf5909a6427592cbe7150c87f5b8.jpg...","email":"...","captchaObfuscationToken":"{\"b64KeyCipherData\":\"...\",\"b64CipherData\":\"...\"}"}} with status code: 200
Hi @bracki , what about the weeks before? Do you have any successes during the last 6 weeks? Is this consistently failing or does it have a high error rate and if so what is that? If this is constantly falling, did you try without the 2 captcha solver to use the interactive one and does that work?
Sadly, if I can't reproduce the issue the only way I can solve this is by having the credentials of the account that fails which is sadly not possible in your case.
It has a very high error rate. Occasionally it works, but most of the time it does not. Haven't tried the interactive one, as this is a part of a cron job.
So this more likely than not is a timing issue. I will have a look this Friday
I double checked all our failures. It's like @rianbk describes. Two attempts and then it fails. The captchaUrl
from the failure message is different than the ones that where processed previously.
Hey @bracki and @rianbk , could you please give https://github.com/schubergphilis/awsapilib/tree/signin-delay a try and let me know if that changes anything for you guys? If yes, then we will need to tweak the delays a bit and see.
@costastf Thanks a lot! I tried it but unfortunately it doesn't change anything. I'll see if it changes with more data.
I will look into it again on Friday and add a few more time outs. Keep me updated with your data.
Hey guys, I am resurrecting this. Apparently aws requires a new field (well, not so new) of metadata1 which is a fingerprinting field for the authentication to work. What I figure is that this was not rolled out everywhere back when you raised the issue and that is why I could not reproduce. Now it is reproducible by me too as raised by #49 also. I will be reporting on the progress on that one if you don't mind, so I will be closing this one for now. Please follow along because I have mostly fixed it (code is really not good still so definitely not suggested but we are getting there.
Hi,
Trying out the library and I'm struggling to get root login working using the following:
Looks like it just does two capchas and dies. Let me know if i can provide anything else