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

Fatal error: Login error: JSON decode fail, 400 - Bad Request. #620

Closed
rjvs7 opened this issue May 17, 2020 · 3 comments
Closed

Fatal error: Login error: JSON decode fail, 400 - Bad Request. #620

rjvs7 opened this issue May 17, 2020 · 3 comments
Labels
duplicate Problem is already described in another issue

Comments

@rjvs7
Copy link

rjvs7 commented May 17, 2020

I'm trying to get the profile info using --login option and it errors out with:

[root@xxxx ~]# instaloader --login xxxx yyyy
Session file does not exist yet - Logging in.
Enter Instagram password for xxxx:
Fatal error: Login error: JSON decode fail, 400 - Bad Request.

How do i create a session file or overcome this issue?

I have enabled mobile code verification on my insta profile.

@tmrwlsn
Copy link

tmrwlsn commented May 17, 2020

I'm having this same problem. I tried different accounts, made sure to get the latest version, even restarted computer. Linux user. Can't say I can help, but you're not alone. Might be a new issue

@Infinitay
Copy link
Contributor

There have been changes regarding the login on Instagram's side and Instaloader's login functionality is currently broken. As long as there does not exist any solution, we can only present the following advice:

  • The workaround described in Troubleshooting - Login Error, which creates the sessionfile from the Firefox cookie database, still works.
  • Always keep your sessionfile. I have never seen a sessionfile expire. If you have your sessionfile, no login is required, and thus, no login can fail.

The snippet posted in this issue to allegedly fix the login error does not seem to work. As always, we are very open to discuss ideas in Pull Requests.

Taken from the fourth issue down prior to the creation of this one.
#615 (comment)

@elrxii
Copy link

elrxii commented May 17, 2020

Referencing: #615 (comment)

@Infinitay thanks for posting the Troubleshooting - Login Error workaround link, however that snippet is outdated as Mozilla has updated their query column names, making the SQL statements fail in that snippet. Also, the path in the script only supports Posix directory paths and not Windows paths. I have created a fix for these things, and I can create a PR for it, but I don't know what issue to link it to. How should I proceed?

NOTE: When executing the work-around script and using: instaloader --login=your_profile_name profile_to_search_for on private profiles I get the return statement of: "user_profile: Private but not followed."

@aandergr aandergr added the duplicate Problem is already described in another issue label May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Problem is already described in another issue
Projects
None yet
Development

No branches or pull requests

5 participants