jauderho / bl3auto Goto Github PK

Hi!

I am running Fedora35.
Regarding the Dockersteops
I think the 3. step should be "docker run -it -v codes:/root/.config/bl3auto/bl3auto jauderho/bl3auto"

Just a small detail as I noticed it does not save this image as bl3auto and that left me confused a bit.
I don't use docker that much and this is basically my first actual use besides TruenasScale stuff.
Hopefully others who might ran into this issue can get it to work this way as well.

Could be that I just did something very stupid in that case let me know.
I also thought this could totally be used on a TruenasScale as automatic key redeemer since that on e uses Docker ;)

In the readme how to set this tool up it suggests setting up Docker and creating a codes folder (or having the docker-compose.yml create it) to store results from previous runs.

This doesn't seem possible or used at all with the prebuilt binaries/.exe releases.

I tried to run the tool to claim a bunch of codes, but it got rate limited, and the next time it ran again it started from the start and was not able to go through the full list, so saving successful/failed attempts even with the prebuilt binaries/executables would seem like a useful feature to me for a simpler setup without Docker.

For use in cron jobs, I only want output if there's an error (can't set up, log in, get platforms, etc...), or if there's an attempt (successful or not) at redeeming a code.

I assume there are others that only want output on an error.

I'm going to accomplish what I want out of this with a bit of grep, but I feel like it might be worth having directly. I propose 3 quiet levels.

q - for cron jobs. Output only on code redemption attempt or error.
qq - Output only on error or code redemption failure.
qqq - no output, just an exit code.

I think this may actually be an issue with Gearbox's site/account. I recently started seeing this error:

ranybody:~/docker/scheduled/bl3auto2$ sudo docker-compose up
[+] Running 2/2
 ⠿ Network bl3auto2_default  Created                                                                                                                                                                        1.3s
 ⠿ Container bl3auto2        Created                                                                                                                                                                       17.0s
Attaching to bl3auto2
bl3auto2  | Setting up . . . . . success!
bl3auto2  | Logging in as '[redacted]@gmail.com' . . . . . failed!
bl3auto2  | Had error: failed to login
bl3auto2 exited with code 0

This is pasted from a fresh recreation of my docker container, using the default compose file you recommend, and using .env as recommended. I get the same error in my primary container. I've removed and recreated both the container and image.

I got the same error when I attempted to execute the Windows command line version of the application, manually typing my email and password.

PS C:\bl3auto-2.2.26-windows-amd64> .\bl3auto.exe
Enter username (email): [redacted]@gmail.com
Enter password        : [redacted]
Setting up . . . . . success!
Logging in as '[redacted]@gmail.com' . . . . . failed!
Had error: failed to login

I reset my password at shift.gearboxssoftware.com and tried the new password again at the Windows command line and in the .env on both containers and the problem persists.

So I'm stumped. It seems to be a problem across machines, across containers and across versions of the application. My guess as a total amateur is that Gearbox has done something to prevent my account from accessing via API(?) entirely.