epicgames-freegames-node VS nginx-proxy

Epic freegames claimer (link) - same idea, scans and claims free Epic games. As it is, this is not working for me. I was able to get it running locally, the issue is that the service notifies you when a captcha needs solving, but the bot detection seems to have outpaced the script and even solving the captchas correctly gives you errors and fails to redeem the game.

There is this one https://github.com/claabs/epicgames-freegames-node. While it doesn't pass every captcha by itself(for me it never does because I'm am hosting it on a VPS), you can set it to send you a discord message or an email with a link so that you can solve the capt has, which for me is much simpler than logging into epic games each time to see the new games and take them

I just recently automated Epic claims using Docker. It's completely worth it. I thought it couldn't save me that much time but it does (especially right now with daily giveaways).

Hi all. I am trying to deploy this container on docker with synology: https://hub.docker.com/r/charlocharlie/epicgames-freegames

Its basically the firefox browser in a docker container. I was trying to replicate https://github.com/claabs/epicgames-freegames-node since it stopped supporting ARMv7

I have an express API that runs on EC2 and I am using nginx-proxy

If Traefik is not your thing Im happily using https://github.com/nginx-proxy/nginx-proxy and sslip.io for local docker compose development.

And then even plain nginx to proxy to non docker services...

(And ipv6 for really short urls. E.g. `example.com.--1.sslip.io` etc)

I wanted to share with you an exciting new tool that simplifies the process of interacting with the NGINX Proxy Manager API. It's a TypeScript tool that generates API requests based on environment variables within a Docker container. This tool is heavy influenced by the https://github.com/nginx-proxy/nginx-proxy but it works with npm.

I use an automatically configuring reverse proxy - there's several to choose from, but the nginx-docker image is really nice, and comes with another image to do automatic SSL with certbot (if you wanted to host things externally).

Docker runs on the 3B+ so you could use this [Github] or the one I have deployed here [NGINX Proxy Manager site] amongst others.

- and this

docker compose + wildcard dns + reverse proxy that covers all widecard subdomains + https://github.com/nginx-proxy/nginx-proxy (not to be confused with nginx itself) then setup a container for each app and set a subdomain for it, you can add ssl if you have a public domain or use self signed certs (but you need to distribute it to all machines and devices)

setting up letsencrypt with nginx-proxy and acme-companion

We use the nginx-proxy docker image. Auto-configuring reverse proxy with support for certbot. Never been easier - just put your domain and certbot details in your container env, and it does the rest.

I just use the nginx-proxy image, makes it all super easy, auto-configuring, and all domain/cert information is stored against the project rather than the proxy.