Open DarkSmileee opened 3 months ago
browser isn't opening to login
I guess your SHOW=1
isn't picked up.
https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt
Try putting it in data/config.env
to see if that's the issue.
Captcha depends on the system, may be due to it being Windows Server, running headless or too many login attempts.
@vogler Actually i've the same issue
and when connecting using the browser, the captcha can't be filled (failed even if done right from VNC browser, probably because they detect we're within a docker container or something :/)
I tried to check if i can generate an Oauth token to login to Epic Game Store instead of user/pass, but it seems not possible
PS : Clicking on trying another login method ask for a captcha as well, so i can't pass it PPS : login is working fine out of the container from my workstation normal Firefox browser
PPS : linking Epic account to Steam allow us to connect to Epic wiht NoVNC using steam login, and code sent by email, well it remove the automated way of doing it, but even inside the NoVPN, when trying to add the game to cart we got an impossible to validate captcha :/
I'm also getting a captcha again on Epic Games with a local install. SHOW=1 works fine for me, when I attempt to solve the captcha it fails every time regardless if it's correct or not.
No captcha when I normally access EPIC Games from Firefox, or their EPIC Games client.
❯ node epic-games.js
2024-08-29 12:43:42.552 started checking epic-games
Adding webgl.disabled to /Users/voglerr/dev/Web/free-games-claimer/data/browser/prefs.js
startup: 3.525s
Signed in as ...
login: 2.370s
Free games: [
'https://store.epicgames.com/en-US/p/gigantic-rampage-edition-03f532',
'https://store.epicgames.com/en-US/p/the-callisto-protocol'
]
Current free game: Gigantic: Rampage Edition
Not in library yet! Click GET.
Claimed successfully!
claim game: 18.324s
Current free game: The Callisto Protocol
Not in library yet! Click GET.
Claimed successfully!
claim game: 14.161s
claim all games: 34.755s
See #183, need automated data collection to get some idea what influences it.
❯ node epic-games.js 2024-08-29 12:43:42.552 started checking epic-games Adding webgl.disabled to /Users/voglerr/dev/Web/free-games-claimer/data/browser/prefs.js startup: 3.525s Signed in as ... login: 2.370s Free games: [ 'https://store.epicgames.com/en-US/p/gigantic-rampage-edition-03f532', 'https://store.epicgames.com/en-US/p/the-callisto-protocol' ] Current free game: Gigantic: Rampage Edition Not in library yet! Click GET. Claimed successfully! claim game: 18.324s Current free game: The Callisto Protocol Not in library yet! Click GET. Claimed successfully! claim game: 14.161s claim all games: 34.755s
See #183, need automated data collection to get some idea what influences it.
From the logs, it shows your fgc install already had epic properly authenticated beforehand. Have you tried with a new fgc installation or clearing the fgc data folder ? The repeated captcha failures happen from the initial login attempt and less often when having established epic session data.
Sometimes I set a fresh browser folder to test the login if something is not working, but haven't done so for some time. I think the last time I also got a captcha during login, I solved it manually and then everything was fine afterwards without captcha during claim.
Interesting, I was unable to log in because the captcha never works. Seeing this I tried with a new browser folder. Had to login again on all services as expected, but all three worked. (Except for the slight problem that the docker thought it was in interactive console mode, which it was not, so id did not realize I logged in in the browser until after a restart)
Sometimes I set a fresh browser folder to test the login if something is not working, but haven't done so for some time. I think the last time I also got a captcha during login, I solved it manually and then everything was fine afterwards without captcha during claim.
I just recently tried exactly this; Freshly installed FGC, Running the browser in both headless and not headless mode; I was prompted to complete the captcha, I did so and on the next claim I again had to complete the captcha again. Still seems like something is being detected during the claim process on EPIC.
Sometimes I set a fresh browser folder to test the login if something is not working, but haven't done so for some time. I think the last time I also got a captcha during login, I solved it manually and then everything was fine afterwards without captcha during claim.
I just recently tried exactly this; Freshly installed FGC, Running the browser in headless mode I was prompted to complete the captcha, I did so and on the next claim I again had to complete the captcha again. Still seems like something is being detected during the claim process on EPIC.
Same here, new to the project!
Sometimes I set a fresh browser folder to test the login if something is not working, but haven't done so for some time. I think the last time I also got a captcha during login, I solved it manually and then everything was fine afterwards without captcha during claim.
I just recently tried exactly this; Freshly installed FGC, Running the browser in headless mode I was prompted to complete the captcha, I did so and on the next claim I again had to complete the captcha again. Still seems like something is being detected during the claim process on EPIC.
Same here, new to the project!
Same for me aswell, I have to manually intervene.
I'm getting this error on login, also browser isn't opening to login, logged in manually in my browser and worked. Running on windows server 2019
Already tried ; npx playwright install firefox --with-deps