python version user 2.7
Paste the output of python -V here:
Code:
# Example code that will produce the error reported
from instabot import Bot
bot = Bot()
bot.login(username="user", password="pass")
followers = bot.get_user_followers(bot.user_id)
Error/Debug Log:
2018-04-11 06:47:42,913 Instabot Started
2018-04-11 06:48:05,527 - ERROR - Request return 400 error!
2018-04-11 06:48:05,530 - INFO - Instagram error message: Sorry, there was a problem with your request.
2018-04-11 06:48:05,531 - INFO - Error type: sentry_block
I suppose that something changed in Instagram authentication, so I'm unable to login to my account with instabot, on the other hand I can login without problem using official Instagram application with same password.
Until yesterday it worked like a charm!
Same story
I verified that on windows platform with Python 2.7.9 and latest version of instabot (0.3.5.3) it works. The problem occurs when I use the library instabot on Ubuntu 16.04.4 LTS with Python 2.7.12
I tried with different public ip addresses and got same KO result with Ubuntu.
same here :worried:
Some more info on this error:
when I first tried to sign in I've got this error
2018-04-11 19:56:02,925 - ERROR - Request return 400 error!
2018-04-11 19:56:02,926 - INFO - Instagram error message: challenge_required
2018-04-11 19:56:02,926 - INFO - Error type: checkpoint_challenge_required
2018-04-11 19:56:02,926 - INFO - Login or password is incorrect.
and only then got:
2018-04-11 19:56:35,247 - ERROR - Request return 400 error!
2018-04-11 19:56:35,654 - INFO - Instagram error message: Sorry, there was a problem with your request.
2018-04-11 19:56:35,654 - INFO - Error type: sentry_block
2018-04-11 19:56:35,655 - INFO - Login or password is incorrect.
100% WORKING SOLUTION!:
just need a breaksentry_block or checkpoint_challenge_required errors)Deactivate for how long? And how to relogin? It is safe?
i have same error
+1
@sudo-judo I've edit my comment. Also you could read more about how instagram deactivation works here
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.
Most helpful comment
same here :worried:
Some more info on this error:
when I first tried to sign in I've got this error
and only then got:
100% WORKING SOLUTION!:
just need a breaksentry_blockorcheckpoint_challenge_requirederrors)