-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Instagram: Can't download public Reel, "Unable to extract username" #5967
Comments
Something has changed on instagram's end. This is not the usual rate-limit block/redirect, their graphql is sending an empty JSON response: {
"data": {
"shortcode_media": null
},
"status": "ok"
} @jazzido Are you able to open this URL in your browser without being logged in? (use private/incognito tab) A possible workaround to download would be to pass EDIT: It seems like only certain IG posts exhibit this behavior. I am still able to browse and download others without being logged in. The |
Thanks for the quick reply, @bashonly
It redirects me to the login page, so no.
That worked prefectly, thanks! |
same issue Example URL: https://www.instagram.com/reel/CnzB0EyPL_3/?igshid=Yzg5MTU1MDY=
|
There seems to be some restrictions because of location. I can download from the link from one country and can't from another |
I can't reproduce for this url, but I can reproduce for https://www.instagram.com/reel/Cw1yI2_SmQf/ (which was shared in #8048). Interestingly, that video is age-restricted, so it's likely just not possible to download that video without cookies |
I think age restriction is at least part of the issue. Because you must be signed in to view age restricted profiles, it needs a valid session. But it's partly geographic too. From a UK or EU VPN server:
From a Swiss, US, Canadian VPN server:
Judging by this it actually seems to get further in the first instance - it gets to the login page and prompts for credentials, whereas it can't seem to find the login page at all elsewhere. |
I just wanted to add the comment here that it is absolutely disgusting that these companies are implementing what surmounts to absolute dogshit tactics whose primary fallout is effectively suppressing independent journalism. On the day of Judgment the CEOs of these organizations ought to be quartered and hung in front of their respective office buildings on a livestream using their own platform. Fuck them so much. May every single bone in their bodies be broken and shoved up their assholes sideways. |
All of the videos that result in this error are not viewable in a browser without being logged in -- I get the same nearly-empty JSON response in my browser too. Workaround: pass Proper solution: raise a better error when we get an API response like this |
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Checklist
Region
No response
Provide a description that is worded well enough to be understood
Reel can't be downloaded
Provide verbose output that clearly demonstrates the problem
yt-dlp -vU <your command line>
)[debug] Command-line config
) and insert it belowComplete Verbose Output
The text was updated successfully, but these errors were encountered: