vogler / free-games-claimer

Automatically claims free games on the Epic Games Store, Amazon Prime Gaming and GOG.
GNU Affero General Public License v3.0
2.46k stars 149 forks source link

Epic no longer loging in #236

Closed DuzAwe closed 11 months ago

DuzAwe commented 11 months ago

Epic login form never auto-fills. I can log in via VNC by providing the email and the script seems to take over again. Works fine for GOG

ezek1el commented 11 months ago

I concur. No longer logging in automatically.

Exception:
locator.innerHTML: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:117:51 {
  name: 'TimeoutError'
}
--- Exception:
locator.innerHTML: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:117:51 {
  name: 'TimeoutError'
}
--- Exception:
locator.innerHTML: Page closed
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:117:51 {
  name: 'Error'
}
--- Exception:
locator.innerHTML: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:117:51 {
  name: 'TimeoutError'
}
carrothu-cn commented 11 months ago

Same problem when setting up epic account.

4n4n4s commented 11 months ago

@vogler elements just for account on top right seem to be gone somehow. Strange thing is when you open it in normal browser they are there.

p6002 commented 11 months ago

Same here, gotify sending some strange notification:

image
mattleh commented 11 months ago

possible solution would be to replace: user = await page.locator('#user span').first().innerHTML(); with: user = await page.getByLabel("Account Menu").getAttribute('Title');

but i'm not sure if the returned value is the same.

lostb1t commented 11 months ago

same problem

--- Exception:
locator.innerHTML: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:117:51 {
  name: 'TimeoutError'
}
vogler commented 11 months ago

They changed the layout. Login is also split in two steps (email/password). Should be fixed now.

lostb1t commented 11 months ago

works for me 👍🏻

p6002 commented 11 months ago

It seems to be working. It would be nice if ctrl+alt+delete buttons via noVNC would restart the container/service. Currently I get a capcha notification on my watch, but when I'm home, the session has expired and I have to log into VM to restart the container so I can fill in the capcha.

vogler commented 11 months ago

@p6002 New issue/discussion? However, I don't see how that should work. Either you solve the captcha right away or you don't in which case it will time out and the container will stop (so also no more VNC). Until #183 is solved, I would just run it directly with node, then there's no captcha.

ezek1el commented 11 months ago

Looks like it is working again. Thanks!

p6002 commented 11 months ago

Either you solve the captcha right away or you don't in which case it will time out and the container will stop (so also no more VNC).

You're right, that's why there should be some option to restart the container, for example via the button in the upper right corner of noVNC ctrl+alt+del which currently does nothing.

Albirew commented 11 months ago

weird, i still have this issue even after a git pull and a docker compose rm...

2023-11-01 09:47:38.825 started checking epic-games
locator.innerHTML: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('#user span').first()
============================================================
    at file:///fgc/epic-games.js:107:51 {
  name: 'TimeoutError'
}
p6002 commented 11 months ago

It works for few days after last issue.

Albirew commented 11 months ago

PS: i noticed a difference between before and now: before: at file:///fgc/epic-games.js:117:51 { now: at file:///fgc/epic-games.js:107:51 { a 10 lines change.

vogler commented 11 months ago

@Albirew Why are you using git pull if you're using docker compose? You apparently didn't update your docker image since your log still says #user span which was removed in https://github.com/vogler/free-games-claimer/commit/d73a523fe7f76608af5db4e72b567f058814fea1.

Albirew commented 10 months ago

uh? what do you mean? i'm using git pull because the docker-compose file contains build: .

my start script looks like this:

docker compose rm -f # delete old container in case of internal changes
git stash -q         # stash docker-compose.yaml for custom command and env_file
git pull             # get latest
git stash pop -q     # push back edited docker-compose.yaml
docker compose up -d # launch with latest version

edit: nevermind, i saw what i was lacking: docker compose pull since there's also an image aside build .

vogler commented 10 months ago

Yea, no need to build the image, it's built on every push. The docker-compose.yml is just an example and likely won't change, so no need for git. The only thing you need to do is pull the new image, so docker compose pull && docker compose up -d.