Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login Failing #33

Open
Enverex opened this issue Apr 12, 2017 · 6 comments
Open

Login Failing #33

Enverex opened this issue Apr 12, 2017 · 6 comments

Comments

@Enverex
Copy link

Enverex commented Apr 12, 2017

Not sure if they've changed anything since the last update here in Jan, but despite correct credentials, the login process is failing. I can see the correct username and password being sent via post (with the exception of the @ in the email being translated to %40 which I assume is part of the form encoding) but I still get the "Either username/password are not correct, or a ReCaptcha..." message.

Adding --auth with the _simpleauth_sess value from the browser doesn't help at all, same error.

The debug output shows a 302 on /home/keys, then a 200 on /login?goto=%2Fhome%2Fkeys then a 401 on /processlogin. _simpleauth_sess in that post matches the one I'm seeing in the browser.

@shakeyourbunny
Copy link

problem still persists, same here.

@KingPin
Copy link

KingPin commented Jun 30, 2017

Same issue here. passing -A didnt help.

graag pushed a commit to graag/humblebundle that referenced this issue Oct 12, 2017
- Add `_le_csrf_token` to the payload sent to the humbleguard. For me
  resolves problems with email code verification.
@graag
Copy link

graag commented Oct 12, 2017

In my case there were actually two problems:

  • It is important to copy all of the _simpleauth_sess cookie including the " ". In my case this looks like this, notice that the AUTH is in additional ' ':
./humblebundle.py --auth='"alotfoacharctersandnumbers"'

@MestreLion
Copy link
Owner

@graag , as I merged PR #35, does it mean this issue is also fixed? can @KingPin and other confirm that login is now working given the new instructions and the _le_csrf_token fix?

@graag
Copy link

graag commented Oct 19, 2017

@MestreLion I guess that the main issue here was with the _simpleauth_sess cookie. Maybe a note in the documentation stating that all characters have to be included?

@monreal
Copy link

monreal commented Jan 14, 2018

Thanks for pointing out the thing about the double quotes, @graag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants