Error: Failed to login

[jameshutt]

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.

[Sonnenheim]

I can confirm the issue.

[squatto]

The API endpoint that is being hit for the login is throwing a 500 Internal Server Error, which is why the login request is coming back as a failure

[jauderho]

Config is here: https://github.com/jauderho/bl3auto/blob/main/config.json

{
    "version": "2.2.26",
    "loginUrl": "https://api.2k.com/borderlands/users/authenticate",
    "loginRedirectHeader": "X-CT-REDIRECT",
    "sessionIdHeader": "X-SESSION-SET",
    "sessionHeader": "X-SESSION",
    "requestHeaders": {
        "Origin": "https://borderlands.com",
        "Referer": "https://borderlands.com/en-US/"
    },
    "shiftConfig": {
        "codeListUrl": "https://shift.orcicorn.com/shift-code/index.json",
        "codeInfoUrl": "https://api.2k.com/borderlands/code/",
        "userInfoUrl": "https://api.2k.com/borderlands/users/me",
        "gameCodename": "oak"
    }
}

If someone can figure out the change in API and submits a PR, I'll accept it. I'm swamped for time right now so I do not have cycles to look further into this for a while.

It may not make much of a difference as the feed for updated SHiFT codes has not been updated since 4/2023. So I suppose someone will have to step up to create a feed to scrape and populate with updated codes.

[Tythesly]

Hope somebody can figure this out

[bmfrosty]

I'm not a developer, but I did inspect it. It's now going to https://shift.gearboxsoftware.com/sessions - and copied it as cURL.

curl 'https://shift.gearboxsoftware.com/sessions' \
  -H 'authority: shift.gearboxsoftware.com' \
  -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/x-www-form-urlencoded' \
  -H 'cookie: update_offer=2; _session_id=e5ed48e5d6461576979b5976ca4d855c' \
  -H 'dnt: 1' \
  -H 'origin: https://shift.gearboxsoftware.com' \
  -H 'pragma: no-cache' \
  -H 'referer: https://shift.gearboxsoftware.com/home' \
  -H 'sec-ch-ua: "Chromium";v="118", "Google Chrome";v="118", "Not=A?Brand";v="99"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: document' \
  -H 'sec-fetch-mode: navigate' \
  -H 'sec-fetch-site: same-origin' \
  -H 'sec-fetch-user: ?1' \
  -H 'upgrade-insecure-requests: 1' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36' \
  --data-raw 'utf8=%E2%9C%93&authenticity_token=9hWkBhL9gfF2QRVhg1FLXl%2Fusdfg5anwfjvrvulHxcXENxLNuc9%2Fd8i22sT5oMvH9xIH9FcOVHbfMgYPmozfgw%3D%3D&user%5Bemail%[email protected]&user%5Bpassword%5D=Password&commit=SIGN+IN' \
  --compressed

[DealsBeam]

Once I enter the password the command window just closes.

[Dyzson]

Is anyone able to fix this or are there any alternatives?

[Forkinator]

So as of right now, there is no way to get this working? Are there any alternatives that work? Hope someone can get back to me ive spent many hours on this.