Charlie Laabs

Can you post your config with the sensitive stuff redacted?

I have a few ideas that I'm just jotting down so I can try out later: - The chromium version may have updated in APK, so I either have to...

I don't think the Chromium version was the issue, as it was already using the correct version. [These docs](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#tips) from puppeteer recommended the `--disable-dev-shm-usage` argument in Alpine, so I added...

The puppeteer docs recommend adding `docker run --cap-add=SYS_ADMIN` to your Docker config. Can you try adding that and see if it's any more consistent? Yeah it's either a race condition...

I published a Debian version of the image to my test tag: `charlocharlie/epicgames-freegames-test:bullseye-slim`. It uses Debian slim and Chrome rather than Chromium. Feel free to test it for consistency. If...

I think this is the same as the various issues mentioned in this puppeteer PR fix: https://github.com/puppeteer/puppeteer/pull/7802 Although Alpine doesn't have Chromium 97 that puppeteer 13.0.0 uses, I think Chromium...

Scratch that, Chromium 96 doesn't run in Alpine 3.14. We'll have to wait a few days until the Node 3.15 image releases. However puppeteer 13.0.0 still seems to operate in...

I added a fix that will retry launching the browser until it actually works. It's kind of a memory risk as it doesn't actually close the failed launched Chromium process...

I think Epic has some sort of AWS WAF bot control policy configured that doesn't like the direct HTTP calls. I see a similar timeout when running on a PIA...

I actually figured out what was causing issues when connecting via my VPN. It turns out my VPN was configured for a lower MTU value than my other network interfaces,...