keithdu45
Registered Member
- Jul 11, 2017
- 53
- 6
Hi, I’m building an Instagram automation bot and I’ve been having an annoying issue.
The bot is using a chrome headless instance controller via puppeteer. The bot browses Instagram, picks users and interacts with them (might open & like a few posts, follow, unfollow). Nothing special.
Overall, it was working well during the first 4 days, then it stopped working correctly on some accounts.
Now when the browser goes to an Instagram profile URL (instagram.com/USERNAME), Instagram shows “Sorry, this page isn’t available” on Windows, and a blank page on macOS.
It seems to happen on almost every Instagram Profile URL the bot goes to (but it doesn't happen on the Feed page for instance). It reminds me of a soft-ban behaviour, but how can I be sure?
Has anyone encountered this issue? And maybe found a solution?
I know that if I use the same Instagram account for automation, same IP, but with a different browser it doesn’t do this anymore and it works fine. But I’m trying to find a way to keep using the same headless chromium instance.
Side note: automation numbers I’m using
1 computer / 1 chromium / 1 instagram account / 1 IP / no proxy / no vpn
Thanks
The bot is using a chrome headless instance controller via puppeteer. The bot browses Instagram, picks users and interacts with them (might open & like a few posts, follow, unfollow). Nothing special.
Overall, it was working well during the first 4 days, then it stopped working correctly on some accounts.
Now when the browser goes to an Instagram profile URL (instagram.com/USERNAME), Instagram shows “Sorry, this page isn’t available” on Windows, and a blank page on macOS.
It seems to happen on almost every Instagram Profile URL the bot goes to (but it doesn't happen on the Feed page for instance). It reminds me of a soft-ban behaviour, but how can I be sure?
Has anyone encountered this issue? And maybe found a solution?
I know that if I use the same Instagram account for automation, same IP, but with a different browser it doesn’t do this anymore and it works fine. But I’m trying to find a way to keep using the same headless chromium instance.
Side note: automation numbers I’m using
'peak_likes_hourly' => 20,
'peak_likes_daily' => 150,
'peak_follows_hourly' => 5,
'peak_follows_daily' => 40,
'peak_unfollows_hourly' => 20,
'peak_unfollows_daily' => 100,
1 computer / 1 chromium / 1 instagram account / 1 IP / no proxy / no vpn
Thanks