-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Error: Too many login attempts. (Captcha issues during login) #97
Comments
Hey ! I also encounter this issue :/ |
Good day, |
Same here but with a slighly other traceback:
|
Also having this issue, same traceback. |
The error message doesn't matter, as the backend Epic captcha system is a black box. I just pushed the ideas I had (1d2f861), but it still doesn't work. I'll have to take another shot at it later. |
Your changes may have broken something. I updated yesterday and now I'm being spammed with captcha emails, getting a new one every time I complete one. |
It seems rolling back to the previous docker image now results in the error message above as well. |
If I wanted to tinker with it to try finding a solution, where would you recommend me to start looking at? @claabs |
The core principal of the whole project is to recreate what Epic's webapp does during login. So we just have to make sure the project does all the same API calls that the webapp does. The only thing I can think is that I could still be missing is a Talon call or payload I didn't catch. |
Came here to report same issue. I was able to get it to run once yesterday by generating a new cookie, but back to the same issues today. I sends me 3 capatacha emails, I run them, and then it fails with too many login attempts. Also running via Docker for what it's worth. If you need any other logs/info, please let me know and I can get them to you.
|
I think I fixed it? Once the build finishes, feel free to pull and try again. Technical notes: I noticed the |
I was able to login and redeem on my server using the latest image. Make sure to pull the latest image to fix this issue. |
This comment has been minimized.
This comment has been minimized.
I just updated the image but still getting the same error. I get 3 mails, every mail/captcha is successful, but after the third one i get the error 17 |
@Joly0 Just to verify, you're on the latest version, run this command: $ docker inspect -f '{{ .Created }}' charlocharlie/epicgames-freegames It should output |
I too still have the same problem, also on the latest version. I am using two accounts, if that matters. |
I think I know what led to the false hope. My browser had gained enough hCaptcha trust to bypass the captcha game. Trying another browser to force the captcha game leads to the same issue. This makes me think it's something to do with some hCaptcha proxy issues, but I'm already proxying everything... |
I think it's known at this point, but updated to latest image and also have the same issue, shoots 3 or 4 captacha emails at me and then says too many login attempts.
|
Btw with the recent update the captcha does not even solve anymore, might be a bug on my end, but it does not solve itself anymore and i dont get a captcha to solve it |
I've considered this, but ultimately, I'd like to just work on a robust solution that wouldn't get shut down by Epic in the future. All it would take for them to defeat it is to enable the feature toggle that requires captchas on purchase. |
@joelang1699 Follow the guide here to setup cookie import: https://github.com/claabs/epicgames-freegames-node#cookie-import |
Solved. Thanks mate! Although I should add the cookies were added less than a month ago. |
I guess I should also give an update on the V4 progress. The big changes it will make are:
|
Discord notification would be absolutely spiffy old boy!
…On 2 Aug 2021, 19:51, at 19:51, Charlie Laabs ***@***.***> wrote:
I guess I should also give an update on the V4 progress. The big
changes it will make are:
- Use headless Chrome automation to login/solve captcha when it
requires
- I'm working on a [puppeteer
plugin](https://github.com/claabs/puppeteer-extra-plugin-portal) that
will essentially open a screencasted portal to the login page, so
you'll just be interacting with the site remotely. I have a working
prototype, just need to publish it and test it in a container
- Finally merge the PR that adds more notification methods (Discord,
Telegram, etc.)
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#97 (comment)
|
@claabs - Let us know when you need testers. Happy to build the container et all myself as required. Thanks again for all the work :) |
It's happening again. I just replaced the cookies last week. Captchas won't solve. |
Also happening for me. It doesn't matter how many times I solve the CAPTCHA correctly, tried the automatic method of obtaining the cookie, manual method, and have even cleared all of my cookies and tried fresh. All I keep getting is more 'solve this' emails. Maybe implementing something like in #124 to the config would help? |
sorry for opening again i get 3 times captcha emails. and then solve them all the container log shows
and this is my config.json
|
@SoraKasvgano Not a wise idea to share your TOTP token, since now anyone can generate your 2fa tokens. I'd delete & setup your Epic 2fa again if I were you |
thanks for advice ....I had changed some keyword s in it before |
Yeah, I think you have to wait until V4 for this to get fixed. I get the same thing. Hopefully V4 comes soon! |
Since it's easy to lose in the above conversation, I'll post again. You can work around the bug by importing the cookies manually. |
I have tried doing using this method on multiple devices as well and I still get the 'too many login attempts' error. |
The manual cookie import method definitely works. Stop and destroy the container, add the cookie file, create a new container. Make sure you are following the cookie import method carefully, both in changing the domain you export the cookie from, and in where you place the file. I just re-checked on the latest version of the container, it's working as expected. Only downside to this method if you need to renew your cookie every month. |
@LilTrublMakr can u give me ur discord or telegram |
I have tried this. I have cleared cookies, cache, destroyed the container, tried a different folder for the container, redoing the config file, even using a different instance of Docker (on my Dietpi). Basically, I have tried everything I can think of short of trying a different computer to log in. I will try on my shiny new Lenovo Legion when it gets here today to make sure that it is the browser (that does weird things anyways).
I have Discord. What is the reason why you are asking? |
Make sure you are creating the cookie in the correct directory and check the log file for an entry saying "converting cookie" or something like that. |
This is the message you should see in the logs if the cookie is correctly configured
|
Since yesterday there seems to be a problem with the login process. For the first time in a few weeks I received a request to solve a captcha. Today I tried again with the newest image version of the container: I solved three of these captchas in a row, after which the logs show the following error:
Full logs from start of the container:
My configuration
The text was updated successfully, but these errors were encountered: