search

claabs / epicgames-freegames-node

Automatically login and find available free games the Epic Games Store. Sends you a prepopulated checkout link so you can complete the checkout after logging in. Supports multiple accounts, login sessions, and scheduled runs.
https://hub.docker.com/r/charlocharlie/epicgames-freegames
MIT License
1.38k stars 93 forks source link

Blank Captcha / Too many Login Attempts #59

Closed Shayughul closed 3 years ago

Shayughul commented 3 years ago

Pulled the latest.

Assuming something is wrong on my end at this point. Hoping somebody can point it out.
I get three emails. All are listed below. No Captcha shows up.
Chrome, Firefox and Edge all on the desktop show no Captcha at all.

On Chrome of my iPhone I get the Captcha to solve but solving it doesn't seem to produce any additional information or different results.

`Incoming env vars: RUN_ON_STARTUP: CRON_SCHEDULE: RUN_ONCE: Getting settings from JSON: /usr/app/config/config.json Setting config variables Run on startup: true Run once: false

epicgames-freegames-node@3.0.0 start /usr/app node dist/src/index.js

[2020-12-24 18:21:13.781 -0600] INFO (38 on 997f24e82dd8): Checking free games for @gmail.com [2020-12-24 18:21:17.194 -0600] INFO (38 on 997f24e82dd8): Action requested. Waiting for Captcha to be solved user: "@gmail.com" id: "63b49682-845e-4556-8106-5010d609978e" [2020-12-24 18:21:17.194 -0600] INFO (38 on 997f24e82dd8): Action requested. Waiting for Captcha to be solved user: "@gmail.com" id: "63b49682-845e-4556-8106-5010d609978e" [2020-12-24 18:21:34.301 -0600] INFO (38 on 997f24e82dd8): Action requested. Waiting for Captcha to be solved user: "@gmail.com" id: "14d6a0e3-eaf2-49df-8da8-d4b8a2ef5636" [2020-12-24 18:21:46.639 -0600] INFO (38 on 997f24e82dd8): Action requested. Waiting for Captcha to be solved user: "@gmail.com" id: "aab3bf68-ef72-469d-9252-8c8ce3a5312b" [2020-12-24 18:21:56.268 -0600] ERROR (38 on 997f24e82dd8): Too many login attempts

Error: Too many login attempts

at Login.login (/usr/app/src/login.ts:101:13) at processTicksAndRejections (internal/process/task_queues.js:97:5) at Login.login (/usr/app/src/login.ts:128:11) at Login.login (/usr/app/src/login.ts:128:11) at Login.login (/usr/app/src/login.ts:128:11) at Login.fullLogin (/usr/app/src/login.ts:205:7) at /usr/app/src/index.ts:20:7 at async Promise.all (index 0) at main (/usr/app/src/index.ts:31:3) Setting timezone: America/Chicago Setting cron schedule as 0 12 * [2020-12-24 18:21:56.268 -0600] ERROR (38 on 997f24e82dd8): Too many login attempts

Error: Too many login attempts

at Login.login (/usr/app/src/login.ts:101:13) at processTicksAndRejections (internal/process/task_queues.js:97:5) at Login.login (/usr/app/src/login.ts:128:11) at Login.login (/usr/app/src/login.ts:128:11) at Login.login (/usr/app/src/login.ts:128:11) at Login.fullLogin (/usr/app/src/login.ts:205:7) at /usr/app/src/index.ts:20:7 at async Promise.all (index 0) at main (/usr/app/src/index.ts:31:3) Setting timezone: America/Chicago Setting cron schedule as 0 12 *`

image image image

claabs commented 3 years ago

The captcha being blank is expected. Due to the magic of how captchas work, much of the time all you have to do is load the page. Once the green text appears, you're good.

As for the login failing, that's where the figurative question marks start appearing. There's absolutely no way to tell what went wrong with an invalid captcha, so the best suggestion I can give is to just wait a while and try again later.

Shayughul commented 3 years ago

I can add a little more the stew. When I check the links on my phone I get a captcha almost every time and am able to solve them and the purchase works. No idea why it works on mobile and not on my desktop/laptop but I will continue to test and see if I can find a pattern.

mikhail5555 commented 3 years ago

I am having the same problem with one of my accounts, would running it in debug logging mode help? I tried enabling 2fa for the account and later disabled it again, which didn't solve it.

mikhail5555 commented 3 years ago

Fun fact: I just re-ran it for the same user, for email for captcha, solved it, and was finally able to login with it. Might have been an temporary 'bug' from epics side?

wuast94 commented 3 years ago

i have the same issue, 3 captcha mails .. all blank or at least i dont need more than open them, and in the log i get Too many login attempts.

i was thinking its my secure password that brakes the config syntax and changed it to 32 Numbers and letters. same result.

double checked everything but no luck. When you need more infos feel free to ask :) im using the latest docker container with the config json. and for the captcha link im using a https reverse proxy with subdomian if it makes a diffrent

SerinitySW commented 3 years ago

The captcha only works on my phone in incognito and when not using HTTPS. Https seems to break it because the captcha is HTTP?

If I do it on my computer in incognito, I get the success message - however it immediately sends me a new captcha and no login is made.

lordfiSh commented 3 years ago 
[2021-01-01 11:55:31.389 +0100] INFO  (38 on 9cca5655a2ce): Checking free games for MAIL
[2021-01-01 11:55:37.047 +0100] INFO  (38 on 9cca5655a2ce): Action requested. Waiting for Captcha to be solved
    user: "MAIL"
    id: "5bdf7f7f-b51f-4f05-8f73-"
[2021-01-01 11:55:53.334 +0100] INFO  (38 on 9cca5655a2ce): Action requested. Waiting for Captcha to be solved
    user: "MAIL"
    id: "71894e56-17ae-444e-95e8-"
[2021-01-01 11:56:15.256 +0100] INFO  (38 on 9cca5655a2ce): Action requested. Waiting for Captcha to be solved
    user: "MAIL"
    id: "8eba04c4-dae6-4101-9899-"
[2021-01-01 11:56:40.762 +0100] ERROR (38 on 9cca5655a2ce): Too many login attempts
    Error: Too many login attempts
        at Login.login (/usr/app/src/login.ts:101:13)
        at processTicksAndRejections (internal/process/task_queues.js:97:5)
        at Login.login (/usr/app/src/login.ts:128:11)
        at Login.login (/usr/app/src/login.ts:128:11)
        at Login.login (/usr/app/src/login.ts:128:11)
        at Login.fullLogin (/usr/app/src/login.ts:205:7)
        at /usr/app/src/index.ts:20:7
        at async Promise.all (index 0)
        at main (/usr/app/src/index.ts:31:3)

same Problem, solved via copying the cookie.

wuast94 commented 3 years ago

OK without changing anything it now worked for me.. Strange😅

BlackQube commented 3 years ago

I had the same problem while using Firefox. When I opened the link inside Crome, it worked like a charme. Hopefully its usefull for anyone.

SeaLife commented 3 years ago

Hey,

im expierencing the same, using HTTP or HTTPs does not change anything for me.. I'll try it again tomorrow in a incognito http chrome.... :)

If this is not working, i try the cookie way :D

claabs commented 3 years ago

@SerinitySW If you're seeing non-secure script issues, make sure that the configured baseUrl is HTTPS. The backend has to proxy the captcha scripts and replace some URLs using the configured base URL, so replacing them with HTTP URLs while viewing the UI on HTTPS will cause some issues.

As for everyone else's issue, Epic Games has some sort of rate limit on captchas. You just need to wait a few hours and try again.

Faust-d commented 3 years ago

So not that I'm trying to necro-post on a old 'issue', but I'm having the exact same problem, and have been for about 2 weeks now. One of my accounts randomly got through when I was using my phone to answer the captcha request after a few days of attempts, and my second account is still just failing every day I try. I generally wait at least 12 hours between attempts.

claabs commented 3 years ago

I believe I fixed the issue (see this post). Comment on #81 if you still experience issues.