How to get out of the challenge verification loop on Instagram?

[Chipi]

Hi everyone, first of all, I want to thank every single person here that took time to post information to help the community. I am FollowLiker user and I have been experiencing this issue since the last thursday. I contacted the support team and they answered this:

"Date: 2017-12-11 06:49:37
Name: Follow Liker Support

Message:

Hello,

Instagram has a bug in their anti-spam system. The issue is not something we can solve. Instagram will resolve it themselves.

Update your FollowLiker installation to version 9.8.0 and try again. If the issue persists, pause the tasks for some days."

I updated the software and it is still not working for me. I use dedicated proxies.

I'll be in touch.

 

[auuuu]

Where do you get a private bot? Costs?

Coded myself

 

[auuuu]

Yes. They have indeed disabled sale.

This was in the footer of their mail :

NOTE: We've not removed the scripts from Codecanyon. We've just disabled them until this issue has been fixed.

-----

I would strongly suggest everyone selling services that depend on bots / automation to pause for a while. No need to panic. Over a 1000 developers are working by this time. There is too much at stake. However - it is very much recommended to pause your sales and temporarily disable it. Again - no need to panic at this time. That will not help anyone.

-----

I am personally contacting everyone I know (big players like FL, MP, VT, NP) - and trying to collaborate with them and share with them ideas.

Here is my suggest to BHW if you want this solved faster -

1. Someone said that Instavast bypassed this issue.
Everyone contact them. Reach out.

2. Most Panels that are marketed on BHW are working.
Please reach out to everyone you can. They seem to have the fix too.
I've personally contacted a few of them I know. Waiting for their reply.

3. Find out how are legit companies able to log in on server via API (Most of these are analytical companies)
They scrape data from Instagram day in and day out via API.
This is a tough one - I have an idea on how they are doing it - but I don't want to discuss something I'm not sure of.

PEOPLE OF BHW - JUST REACH OUT - SHARE INFO - COMMUNICATE - THERE IS A WAY - PEOPLE HAVE WORKED AROUND THIS.

THE ONLY ONLY ONLY WAY YOU CAN HELP AT THIS POINT IS BY COLLABORATING WITH THOSE WHO HAVE IT WORKING.

EVERYONE ELSE JUST TALKING AND COMPLAINING - THAT IS NOT HELPING.

IF YOU ARE TRYING YOUR OWN METHOD AND FAILING - SHARE THOSE TOO - SO WE CAN ALL ELIMINATE CERTAIN POSSIBILITES AND VERIFY WHAT DID NOT WORK IF MULTIPLE PEOPLE FAILED AT IT.

Once again - be patient. Some of the best developers around the world are working on this.

As far, the only one member here that is focusing hard on solving this. Thank you so much!

 

[tlgsn]

Final Status;
VPN, Proxy, Server IP, Home IP (City IP) = Not working.
Mobile IP (Vodafone etc.) = Working.

It's like a bug or data collection. 5 days I try every method. Most of the time, official applications can not log in. The problem is definitely related to the IP address.

Do not worry. It will be resolved soon. Or Instagram will get the bug. I'm following. Please share your knowledge.

 

[AbuShobak]

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!!

 

[202GreatDays]

It is a reported BUG with Instagram's Anti-Spam System according to Follow Liker.

- Updating to Follow Liker version 9.8.0 does not work
- Changing IP/Proxy does not work
- Email "Account Auto Unlocking" on Follow Liker does not work
- Trying a different software does not work

This is a persistent issue.

All you can do is wait this one out.

Fingers crossed.

 

[dicekid]

followliker updated their software to 9.8 but didn't solve the issue
wondering what the point of it

 

[bournemarketer]

I had this issue with followliker on my AWS server. I am now using Jarvee from my home computer and it is working fine. I did not try FL on my home computer because there was a DB error from copying over the DB files.

 

[Cognitive]

I don't think that all this mess has something to do with the IP/ proxy you're using.

I've just checked one of my old Instagram bots and it works smoothly on multiple accounts, both with or without proxy. Not to mention that the proxies I've used in this test are cheap backconnect data-center over-abused IP's (just to make an idea about these cheap proxies: if I am trying to do just 1 search on google with these proxies I am instantly getting a recaptcha). But IG works well, logged in on several accounts multiple times yesterday and today and did some regular activity on each account (follow/ unfollow, likes etc).

PS: this bot is not using IG API.

 

[rootjazz]

It is a reported BUG with Instagram's Anti-Spam System according to Follow Liker.

- Updating to Follow Liker version 9.8.0 does not work
- Changing IP/Proxy does not work
- Email "Account Auto Unlocking" on Follow Liker does not work
- Trying a different software does not work

This is a persistent issue.

All you can do is wait this one out.

Fingers crossed.

Unlikely, a bug that seemingly effects only bots and then mostly only those using proxies. Pretty damned good "bug" for them if so. why would they fix it? If it was a bug, twiitter would be in uproar if 1% of real users were effected, their not, there is nothing on twitter.


Everything I've seen, points to proxy identification on a mass scale and acted upon.

 

[freakingout]

PS: this bot is not using IG API.

Of course, your result is no news. Because we have figured out already that the new antispam currently only targets IG API based logins that are connecting from server/proxy IPs! We already know that website based bots are working from any IP, but that doesnt matter. What is scary is that IG somehow knows what IP is bad and what IP is good and that is bad news for us all! Right now they only apply it to API logins but even website based bots can easly be targeted next if they decide to enable it for the website too!

 

[rootjazz]

I don't think that all this mess has something to do with the IP/ proxy you're using.

I've just checked one of my old Instagram bots and it works smoothly on multiple accounts, both with or without proxy. Not to mention that the proxies I've used in this test are cheap backconnect data-center over-abused IP's (just to make an idea about these cheap proxies: if I am trying to do just 1 search on google with these proxies I am instantly getting a recaptcha). But IG works well, logged in on several accounts multiple times yesterday and today and did some regular activity on each account (follow/ unfollow, likes etc).

PS: this bot is not using IG API.

If you are using the website, then the website is not as fussy / has not had this update applied to it yet as was already more restricted than the mobile API.

 

[ProfitAdvisor]

Also with **** still none update and unfortunaly still location verify loop

 

[freakingout]

If you are using the website, then the website is not as fussy / has not had this update applied to it yet as was already more restricted than the mobile API.

Like you said... "pretty damn good bug"

If it was truly "just a bug" in their code that does checkpoint validation then it would happen on their website too... not just the API.

Isnt it awfully suspicious that it only affects API logins and only when we connect from botnets/proxies/servers?

Looks more like IG knows exactly who we are and have decided to block API logins for the moment... and probably planning to do more after they are done torturing us in this 1st step...

Im almost starting to accept the idea that all my accounts (which have used my proxies) may be on a list now and later get a banhammer when I least expect it

 

[Cognitive]

Of course. Because the new antispam currently only targets IG API based logins that are connecting from server/proxy IPs! We already know that website based bots are working, but that doesnt matter. IG somehow knows what IP is bad and what IP is good and that is bad news for us all! Even website based bots can easly be targeted next if they decide to enable it for the website too!

It's hard for me to believe that they would be super-restrictive in which regards the IP from which a device is comunicating with their API and would have left their website unprotected.

If you are using the website, then the website is not as fussy / has not had this update applied to it yet as was already more restricted than the mobile API.

Well, the web based bot works just fine for me, even if it is loaded with super-cheap crappy proxies.


Anyway...just sharing my personal experience here and trying to suggest that some other problems might be involved in this 'crisis'.

 

[freakingout]

It's hard for me to believe that they would be super-restrictive in which regards the IP from which a device is comunicating with their API and would have left their website unprotected.
Well, the web based bot works just fine for me, even if it is loaded with super-cheap crappy proxies.

It is easy for me to believe why the website is currently less protected. there can be many reasons...

1. the api emulates a phone (android or iphone)
2. why would a "real phone" connection be coming from HighProxies or OVH servers, for example? that is super suspicious! no real people do that!
3. so... "ban suspicious proxies on the mobile API!" is an easy choice for them!
4. but the website? the website is already more restricted (you cant do much bot damage with it, it has less features than the mobile API and bot actions are slower via browser because it has much stronger limits for actions per hour etc), so there is less need to ban people from using the website API...(yet)
5. and some real people may be browsing the web via a proxy anyway so it makes sense that they currently allow all proxies on the web login... at least for now.....
6. they may want to test this new system on mobile first (where bots are super suspicious), and then evolve it so they can add it to the website later without affecting real users there either
7. and perhaps there is lots of work involved with adding antispam to their website code, so they decided to do the critical area 1st (mobile API) and worry about website later... instagram has infinite time and money to add it to the website too, later, after the mobile part is done and successful... ;\
8. perhaps the API version is just the 1st test before they go wider
9. everything at insta seems to prioritize the worst areas 1st... and that is clearly the mobile API since almost every bot software uses it.

Know what I just realised? I think Insta may want us to waste our time rewriting all of our bots to use the website instead. So that they can laugh when they enable spamguarding on their site too

 

[rootjazz]

Like you said... "pretty damn good bug"

If it was truly "just a bug" in their code that does checkpoint validation then it would happen on their website too... not just the API.

No I don't think so, they are different systems.

but I don't think it is a bug. It is targeted anti spam protections / investivations /data gathering

It's hard for me to believe that they would be super-restrictive in which regards the IP from which a device is comunicating with their API and would have left their website unprotected.



Well, the web based bot works just fine for me, even if it is loaded with super-cheap crappy proxies.


Anyway...just sharing my personal experience here and trying to suggest that some other problems might be involved in this 'crisis'.

the website is already protected. It has much more restrictive rate limits (you can do less in a minute than the app, you can do less per 24 hours etc etc) and has less features - or did been a while since I looked but there was no image upload / no DMs etc etc

 

[freakingout]

No I don't think so, they are different systems.

but I don't think it is a bug. It is targeted anti spam protections / investivations /data gathering

Yes brother thats what I mean, sorry my english isnt great

I meant that I do not think its a bug and I think the only reason website is ok for now is as you say: the website is a different code system on their server which just doesnt have the new code yet.... but I think the website will soon be guarded too

 

[rootjazz]

It is easy for me to believe why the website is currently less protected. there can be many reasons...



Know what I just realised? I think Insta may want us to waste our time rewriting all of our bots to use the website instead. So that they can laugh when they enable spamguarding on their site too

lol epic troll if so

 

[freakingout]

lol epic troll if so

the reason I think they like to troll is because it looks like they are already trolling us with hte error they give us: endless loop of "suspicious login attempt: china, ukraine, italy, denmark"... grr, it looks like Instas antispam team is having fun with us :\