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

Response code is 429 #1000

Closed
jayeshgniyes opened this issue Nov 23, 2021 · 13 comments
Closed

Response code is 429 #1000

jayeshgniyes opened this issue Nov 23, 2021 · 13 comments
Labels

Comments

@jayeshgniyes
Copy link

jayeshgniyes commented Nov 23, 2021

Getting this error in all pages. Api was working fine just stop working without any changes
Uncaught InstagramScraper\Exception\InstagramException: Response code is 429. Body: <title> Page Not Found • Instagram </title> <script type="text/javascript"> (function() { var docElement = document.documentElement; var classRE = new RegExp('(^|\s)no-js(\s|$)'); var className = docElement.cl

@jayeshgniyes
Copy link
Author

I used a searchAccountsByUsername.php it was working fine but it's stop working from yesterday.

@Koha2014
Copy link

Same problem. As far as I understand, Instagram is blocking requests. Everything goes fine from the local machine. I tried through the withCredentials () function, but there are messages about a suspicious login attempt on the instagram side. I confirm, but the following request also raises suspicions on Instagram. Perhaps it's time to give up this venture

@fageapp
Copy link

fageapp commented Dec 9, 2021

Same problem.

@Koha2014
Copy link

Koha2014 commented Dec 9, 2021

Same problem.

Try this variant:

  1. Authorise in instagram via browser
  2. Get Session ID from Cookies

$instagram = \InstagramScraper\Instagram::withCredentials(new \GuzzleHttp\Client(), '', '', null);
$instagram->loginWithSessionId(YourInstagramSessionid);

Important. Upgrade this extension to last version

@fageapp
Copy link

fageapp commented Dec 9, 2021

Same problem.

Try this variant:

  1. Authorise in instagram via browser
  2. Get Session ID from Cookies

$instagram = \InstagramScraper\Instagram::withCredentials(new \GuzzleHttp\Client(), '', '', null); $instagram->loginWithSessionId(YourInstagramSessionid);

Important. Upgrade this extension to last version

an error occurs

Fatal error: Uncaught InstagramScraper\Exception\InstagramAuthException: Login with session went wrong. Please report issue. in /home/rudis/www/test3/src/InstagramScraper/Instagram.php:2038

@skmachine
Copy link

Instagram is very picky on your ip address.. Try https://github.com/skmachine/instagram-php-scraper it uses proxy rotation and works pretty reliable now.

@svonjoi
Copy link

svonjoi commented Dec 26, 2021

Instagram is very picky on your ip address.. Try https://github.com/skmachine/instagram-php-scraper it uses proxy rotation and works pretty reliable now.

I am trying to follow 200 accounts at once. I'm getting this error after looping follow method and after it reached 40 follows it giving me this error. So your solution with proxies will solve that? Or my scenario instagram will block anyway like spam?

Thanks you

@svonjoi
Copy link

svonjoi commented Dec 26, 2021

or if anybody knows, how many seconds i should wait between each follow/unfollow method execution to avoid this "ban"?

@beshoo
Copy link
Contributor

beshoo commented Dec 26, 2021 via email

@svonjoi
Copy link

svonjoi commented Dec 26, 2021

You can not do that, Instagram will ban follow a action 24 hours... Then ban the account.

So in other words, if im getting this message, my acc will be banned while this 24 hours passing? or this is a warning, and if i still attempting that, ill get ban?

@svonjoi
Copy link

svonjoi commented Dec 26, 2021

Then ban the account.

= permanent account ban, if I understand you correctly

I didnt find nothing about permanent account ban, can you share source please?

PD. I dont understand how this work (liking, following , etc) with this library if i havent create token, client id, etc....?

@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 2, 2022
@stale stale bot closed this as completed Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants
@beshoo @Koha2014 @fageapp @svonjoi @jayeshgniyes @skmachine and others