question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

400 Bad Request - aborted pulling info URL

See original GitHub issue

Starting over the weekend, Instaloader has begin giving an error. Prior to that, no error was being generated and initial downloads were all completed succesfully.

The command line I am running is:

/usr/local/bin/instaloader --latest-stamps .stamps/<profile>.stamp --login <my_user> --no-metadata-json --no-captions --stories --no-video-thumbnails --abort-on=302,400,429 ‘’ <profile>

Here is what I am seeing:

Using latest stamps from .stamps/<profile>.stamp.
Loaded session from /home/<user>/.config/instaloader/session-<user>.
Logged in as <user>.
Traceback (most recent call last):
  File "/usr/local/bin/instaloader", line 33, in <module>
    sys.exit(load_entry_point('instaloader==4.9.1', 'console_scripts', 'instaloader')())
  File "/usr/local/lib/python3.10/site-packages/instaloader/__main__.py", line 471, in main
    _main(loader,
  File "/usr/local/lib/python3.10/site-packages/instaloader/__main__.py", line 212, in _main
    }.get(target[0], 'username')
IndexError: string index out of range

If I run it with --quiet, I get a different error:

Download aborted: Query to https://i.instagram.com/api/v1/media/<profile_ID>/info/ responded with "400 Bad Request".

It appears to be doing this for all of the profiles I am downloading ( ~6 ).

I am getting some of the images and stories images/videos, but it doesn’t look like I am necessarily getting them all.

Instaloader version: 4.9.1

Any suggestions or is anything else seeing something like this?

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:10 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
afterdelightcommented, Jul 18, 2022

yeah this is happening to me too lately, any way to fix it???

1reaction
angentanewbecommented, Jul 29, 2022

Warning: If error 400 occurs and you continue using your account with instaloader or any scraper this will lead to suspension of your account. My account got suspended today. I was downloading my saved posts but Instagram randomly gave error 400 and then when I logged into my account in the Instagram app I found that my account is suspended. So please continue scraping with fake or temporary Instagram account.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix a 400 Bad Request Error (Causes and Fixes)
The HTTP error 400 can occur due to incorrectly typed URL, malformed syntax, or a URL that contains illegal characters. This is surprisingly ......
Read more >
400 Bad Request
400 Bad Request - aborted pulling info URL. ... Coming soon: A brand new website interface for an even better experience!
Read more >
400 Bad Request Error: What It Is and How to Fix It
The 400 Bad Request Error is an HTTP response status code indicating that the server was unable to process the request sent by...
Read more >
400 Bad Request Error · Issue #4513 · axios/axios
Describe the issue I have developed an Discord AI Chatbot, everything worked just fine until now, the bot gives no response due to...
Read more >
axios 400 bad request
I have react component in were Im posting data in djnago back end, but it always gives me 400 bad request as response...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found