-
Notifications
You must be signed in to change notification settings - Fork 800
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
getMedias() not working (404) #196
Comments
Apparently, this API is down by Instagram... I open an issue too. I hope there is another way to get medias See my issue #195 for details about this |
The same issue. |
@raiym this example shows the same error:
|
The same problem. Yesterday all was ok, and today getMedias() get 404 error on any public account. |
looks like they removed it. I believe the https://www.instagram.com/graphql/query/?query_id=17888483320059182&variables=..... could be used instead |
For any account I try, getMedias() is returning a 404. These accounts definitely exist, maybe the IG endpoint has since changed or I have hit some anti-spam measure? I'm also using the latest version 0.8.0 but have tried in 0.7.2 and had the same issue.
Fatal error: Uncaught exception 'InstagramScraper\Exception\InstagramException' with message 'Response code is 404. Body: <!DOCTYPE html> <!--[if lt IE 7]> <html lang="en" class="no-js lt-ie9 lt-ie8 lt-ie7 not-logged-in "> <![endif]--> <!--[if IE 7]> <html lang="en" class="no-js lt-ie9 lt-ie8 not-logged-in "> <![endif]--> <!--[if IE 8]> <html lang="en" class="no-js lt-ie9 not-logged-in "> <![endif]--> <!--[if gt IE 8]><!--> <html lang="en" class="no-js not-logged-in "> <!--<![endif]--> <head><meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title> Page Not Found • Instagram </title> <meta name="robots" content="noimageindex, noarchive"> <meta name="mobile-web-app-capable" content="yes"> <meta name="theme-color" content="#000000"> <meta id="viewport" name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, minimum-scale=1, maximum-scale=1"> in
The text was updated successfully, but these errors were encountered: