- Aug 4, 2016
- 650
- 235
Still verify location loop on ****
Last edited by a moderator:
How to get out of the challenge verification loop on Instagram?
- Thread starter adventurouslover
- Start date
locosantos
Regular Member
- Jul 14, 2017
- 234
- 52
i tried, it doesn't work for me
xWGx
Regular Member
- Sep 28, 2017
- 360
- 334
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.
freakingout
Newbie
- Dec 11, 2017
- 45
- 16
This kind of misinfo must stop, its not helping the situation. Verification codes WERE TOTALLy WORKING NORMALLY 3 days ago, 2 days ago, 1 days ago, today. If you connect from HOME NETWORK IPS, it is all OK! 1 challenge = 1 answer = always success from home IPs eveyr time (I tried and many friends tried)... Only exception to this rule is when you try to connect to a looped bot-account from home after you just got looped via a server (in that case it will not work from home either because the acc itself gets temporarily flagged by the attempted server logon, but if you are patient and wait that acc will work from home later if you retry a day later).
Read htis post, whatever this is it STRONGLY affects bot IPs but zero normal people:
blackhatworld com/seo/how-to-get-out-of-the-challenge-verification-loop-on-instagram.992747/page-8#post-10641190
blackhatworld com/seo/how-to-get-out-of-the-challenge-verification-loop-on-instagram.992747/page-9#post-10641971
I dont trust logons until w eknow for sure why instagram was giving challenge loops only to our bot SERVERS AND PROXIES . this problem targets bot IPs, even from new and unused proxies which had never even connected to insta in the past, which means they are now either banning some hosts/proxies companies or maybe simply banning all nonresidential IPs.
bot logins work from home IP (success after 1 checkpoint), fail from server IP (trapped in checkpoint loop) = even though exactly the same code and API runs on home and server = the only difference is the IP = instagram MUST be looking at server IP somehow
at this point i dont trust any random successwe may have at logons because we already know they detected all of our IPs and are watching all of them, so they may just let some of us login to toy with us or to trap us and grab more data about us.....
ig controls their servers and can see our IPs and collect statistics about what networks are used by spammers, so I guess it was only a matter of time until they start cracking down on bot IPs I guess
Sorry, I know you are just trying to help but it's important that we stick to facts
Last edited:
LeftyLuke
Regular Member
- Jun 13, 2017
- 281
- 62
I am not doing any engagement automation on my accounts atm, I do use an autopost tool. All but 1 account had a verification loop, it was the only one that was not hooked up to one of my proxies but instead was running on one of theirs. As soon as I hooked it up on one of my own proxies the loop ended..
CloudOfSmoke
Newbie
- Dec 11, 2017
- 1
- 0
Greetings everyone
Has anyone tried the verification method without password through Chrome extension?
Has anyone tried the verification method without password through Chrome extension?
xWGx
Regular Member
- Sep 28, 2017
- 360
- 334
Contact Instavast and get the news for all of us.Any news ?
I have personally mailed out to 100 people so far. All those who replied I have copied their reply on this thread to keep everyone updated.
Get the news. Waiting on you.
Contact SMM panels that are working.
If everyone would take the initiative this would be solved sooner.
Follow liker is giving you the error "EMAIL"?
Where do you get a private bot? Costs?
blackhatgorilla
Regular Member
- Nov 13, 2017
- 236
- 97
I'm not sure which panels really work "fine" but none of the last 5 panels i use can solve orders of 1k, 5k, 10k to 40k without problems, every followers going lost or even better, they don't deliver it and change the status to "complete" without any information/news whats going on or how to place future orders, panels are working up to maybe 24%, they buggin too! (i have customers waiting for deliveries since friday. for example just a "light" 500 delivery isn't delivered since 2 days) - i would also say, just keep everything stopped and would recommend any panel to be real enough to say "pause it" "don't order" "wait" or anything else, none panel has any further information whats going on, they just saying "everything works fine" but i wouldn't say that. even some ticket system are suddenly "bugging"
OSolution
Regular Member
- Jul 30, 2017
- 295
- 64
Dang, instadub ain't one of the big players?!
You don't even know if the true developers of those programs are outsourced.
Anyways, just messing...
But this is what the developer of Instadub @rootjazz states...
"Findings so far are indicating it is proxy based.
I have tested 2 accounts that were on proxy, wiped cookies and forced login. They are looping the verification process.
I took 2 accounts that were on proxy, wiped cookies AND removed proxy (so using local IP). They were asked to verify, but it went through.
I then tested a like action and a follow action (1 item each) and both worked.
I then reassigned the original proxy to the account and the proxy now works....
From reading around, the consensus seems to be the verification checkpoint / login pages have the proxy detection code running. Which is causing the looping, bypassing that with a good IP, means you can then use the proxy...
However, how good that is to associate your local IP with the account that was / will be proxied I don't know
This raises the issue of those with many bulk accounts, are not going to be able to do this, only actual / genuine accounts... (logging into 100 accounts on local IP not a good idea, not such a big deal for 3-4+ accounts)
Everyone reports the website still works with proxy for all accounts. So a stop gap measure until more is found out, the above hypothesis confirmed, might be to automate follow / like on the website??? - although maxitems per day will be a lot less than mobile"
freakingout
Newbie
- Dec 11, 2017
- 45
- 16
Great info! thanks! Hmm this quoted part is the exact thing I am worried about too! (what insta will do if we login at home and move cookies to server). they clearly detect the server, so what good will it do to make a login at home and move it to a bad server? since instagram knows our IP (and of course they do) then they can already stop all of our bots instantly if they truly want to log out our old ones, since the proxy IP is the problem, so I am not sure what point there is in moving sessions from a clean IP to the unclean server
I think the only reason they have not logged out or permabanned all of our old bots yet is because they are still testing this new antispam and collecting data :\
If you look in your Insta cookies, you will find this scary one:
{"Name":"urlgen","Value":"\"{\\\"time\\\": 1513020296\\054 \\\"41.54.121.39\\\": 8473}:3jid
_92d9dj2_2d6d5d8gg\"","Domain":"i.instagram com","Path":"\/","Max-Age":null,"Expires":null,"Secure":false,"Discard":false,"HttxOnly":false}(I fake the ip above to protect my proxy, but you get the point...)
in that cookie, insta keeps a list of every IP that has logged in with this usersettings device data
if you make a session at home (a new login) then move it to a proxy, instagrams "urlgen" cookie above will have 2 IPs instead: home ip and proxy IP.
this proves that doing this "home login" workaround for the login issue is still able to be fully tracked by instagram. they will fully see "they login from ok ip, use from bad ip"... and the only reason it works is because right now they are blocking proxy login but it's just a matter of time before they do more with our proxies... like a big banhammer... fuck
Last edited:
rootjazz
Elite Member
- Dec 21, 2012
- 3,166
- 1,190
No, not really. We've never advertised / promoted at all which has kept numbers down but meant I can reply personally to emails and support questions over the years, plus gravitated towards more technical users who wanted to do more technical things rather than the bulk markets of: scraper followers_of and needlessly follow them all, include 40% of which being fake / spam accounts.
Anyway, couple of people have got back saying waiting a few hours after last looped verification attempt, logging in without proxy from local IP works, then can set the proxy again and carry on.
Which is looking like it is proxy detection and not a bug server side... but perhaps it is only coincidental. As always, when big changes happen, lay off things for a while, let the dust settle then reappraise
freakingout
Newbie
- Dec 11, 2017
- 45
- 16
thats what I am doing ;\ all my bots are down. sigh
There is ONE final fix that is pretty complicated but I know it will solve the issue. I am coding on it. If it works - I will share in detail on what I did. And no - no need to pay and shit. DO NOT PAY ANYONE. These scammers love when people panic - they make money in such times. So chill. It will be alright.[/QUOTE]
How do I update followliker? And also have it store my current projects..?
rootjazz
Elite Member
- Dec 21, 2012
- 3,166
- 1,190
Great info! thanks! Hmm this quoted part is the exact thing I am worried about too! (what insta will do if we login at home and move cookies to server). they clearly detect the server, so what good will it do to make a login at home and move it to a bad server? since instagram knows our IP (and of course they do) then they can already stop all of our bots instantly if they truly want to log out our old ones, since the proxy IP is the problem, so I am not sure what point there is in moving sessions from a clean IP to the unclean server
I think the only reason they have not logged out or permabanned all of our old bots yet is because they are still testing this new antispam and collecting data :\
If you look in your Insta cookies, you will find this scary one:
{"Name":"urlgen","Value":"\"{\\\"time\\\": 1513020296\\054 \\\"41.54.121.39\\\": 8473}:3jid
(I fake the ip above to protect my proxy, but you get the point...)
in that cookie, insta keeps a list of every IP that has logged in with this usersettings device data
if you make a session at home (a new login) then move it to a proxy, instagrams "urlgen" cookie above will have 2 IPs instead: home ip and proxy IP.
this proves that doing this "home login" workaround for the login issue is still able to be fully tracked by instagram. they will fully see "they login from ok ip, use from bad ip"... and the only reason it works is because right now they are blocking proxy login but it's just a matter of time before they do more with our proxies... like a big banhammer... fuck
All very true. For those running 100s of accounts it is not a solution. For those running 4-5 accounts from a server instead of having to have their machine running, it might be a solution.
As always, I doubt ISG really care about someone automating genuine accounts, posting images on schedule to their business accounts. these automations do not degrade the ISG service to others
However, they do care about people spamming comments / DMs / spam uploading the same images, bulk following to the limit whether targeted well to the niche or not.
Mass banhammers have happened in the past and will happen in the future, this is just how it is. This is a game, sometimes we win, sometimes they win, they have a new defense, a new way around it is formulated.
WiggleRoom
Newbie
- Dec 11, 2017
- 2
- 4
Hey, I'm an independent Instagram bot creator myself. Mine just follows and unfollows with a web UI, very small scale.
Felt like googling about the issue and found this thread, didn't know so many other bots existed using the mobile API. Kinda cool really
Ran into this problem as well on my server. I've always initiated login from my AWS instance to get a valid cookie and then forward all new requests through rotating proxies for my clients.
One thing I'd like to bring up is the device_id, or the uuid we generate for Instagram requests. For new customers I always generate a new device_id and continue to use that one for every request ever afterwards.
I think the device_id is important. I was unable to get past the checkopint_challenge_required issue on my accounts in my testing until I included the same device_id I used from my personal phone for one of my main accounts. Plan to test this theory more today. Anyone know how each device_id is generated?
Another honest guess is that Instagram is blocking any logins from IPs with *very low account creation calls* with respect to other types of API calls. Might need to get some residential proxies to initiate the sessions, seems to be our only hope.
Been using v16 of API. v17 and up seem to do some weird double signing to the requests that I didn't manage to figure out. At this point it hardly seems worthwhile.
Felt like googling about the issue and found this thread, didn't know so many other bots existed using the mobile API. Kinda cool really
Ran into this problem as well on my server. I've always initiated login from my AWS instance to get a valid cookie and then forward all new requests through rotating proxies for my clients.
One thing I'd like to bring up is the device_id, or the uuid we generate for Instagram requests. For new customers I always generate a new device_id and continue to use that one for every request ever afterwards.
I think the device_id is important. I was unable to get past the checkopint_challenge_required issue on my accounts in my testing until I included the same device_id I used from my personal phone for one of my main accounts. Plan to test this theory more today. Anyone know how each device_id is generated?
Another honest guess is that Instagram is blocking any logins from IPs with *very low account creation calls* with respect to other types of API calls. Might need to get some residential proxies to initiate the sessions, seems to be our only hope.
Been using v16 of API. v17 and up seem to do some weird double signing to the requests that I didn't manage to figure out. At this point it hardly seems worthwhile.