* FAILED: Post data: accounts/login: 400 {"message": "checkpoint_required", "checkpoint_url": "https://i.instagram.com/challenge/xxxxxxxxxx/", "lock": true, "status": "fail", "error_type": "checkpoint_challenge_required"}
ISG require you verify your account
Checkpoint: https://i.instagram.com/challenge/xxxxxxxxxxxxxxx
Has it been solved for you now?Instagram just released a new update for their official app, so I checked out the accs in FL but still same problem. And with the new update of FL it gives me "ERR" next to the accs instead of "EMAIL"
Hope the coders find a solution with the new update and get things back to normal. It's just a nightmare!!
Same for me in FLOK...unless I am doing something wrong in Instaub. There is no loop anymore, yet it doesn't matter from what I'm experiencing.
I can put the verification code in the browser and I can log in via a browser - even though it's through a proxy.
Yet, that 'confirmation' doesn't seem to 'save' in Instadub.
And I get that same message in the logs.
Code:* FAILED: Post data: accounts/login: 400 {"message": "checkpoint_required", "checkpoint_url": "https://i.instagram.com/challenge/xxxxxxxxxx/", "lock": true, "status": "fail", "error_type": "checkpoint_challenge_required"} ISG require you verify your account Checkpoint: https://i.instagram.com/challenge/xxxxxxxxxxxxxxx
No yetHas it been solved for you now?
I am starting to really worry.. If this really is a bug on instagrams side. Than they wont change it. This has a great "Side effect" for them. I dont see why they would change it.. Mark has now almost successfully f_cked us all. He can now successfully charge us and our clients for ads on instagram... This is what he wanted.
Hopefully some smart people on here can design a workaround. I would love to believe that there is still hope..
Come on guys
So quick update guys. I added 40 new accounts 6 days ago, out of that 40, 32 got a please verify request. When this happened I tried to verify 4 of the accounts and nothing worked and I gave up out of frustration. Just now I went back and the accounts I did not follow up on received emails saying "We see you have had some trouble logging in" as the title, or something to that effect, I followed that email and it had me login and now all of those accounts are working. So it seems as if when the loop came up either Instagram flagged the accounts I attempted to verify immediately or somehow attempting to verify those accounts has them stuck in this glitch.
Any update?
When you log in using the android emulator, do you use the same proxy the account was using on FL or a different one?I managed to get 117/120 back. I log in in android emulator using proxy first. Then FL with same proxy.
New one. One account per proxy.When you log in using the android emulator, do you use the same proxy the account was using on FL or a different one?
Where do I get android emulator?New one. One account per proxy.
Try logging out and back in again on browser. You will get the verify againOK...unless I am doing something wrong in Instaub. There is no loop anymore, yet it doesn't matter from what I'm experiencing.
I can put the verification code in the browser and I can log in via a browser - even though it's through a proxy.
Yet, that 'confirmation' doesn't seem to 'save' in Instadub.
And I get that same message in the logs.
Code:* FAILED: Post data: accounts/login: 400 {"message": "checkpoint_required", "checkpoint_url": "https://i.instagram.com/challenge/xxxxxxxxxx/", "lock": true, "status": "fail", "error_type": "checkpoint_challenge_required"} ISG require you verify your account Checkpoint: https://i.instagram.com/challenge/xxxxxxxxxxxxxxx
Existing accounts that hit the loop can't be used at the moment as once they hit the loop they are done for is my experience so far
The only method I have seen is using a valid ip (e.g home ip) to login but that seems risky for the valid ipno, not really, there are methods to get them back and some software devs already solved this problem.
The only method I have seen is using a valid ip (e.g home ip) to login but that seems risky for the valid ip