Can we reset id to unfollow block

Wow, I remember making a Topic about this, but can’t access to it again ! :o

Makes sense bro, you reckon using the embedded browser to follow is safe compared to using the API?

Hey Kgnkr,

It isn’t the device ID that causes the action blocks, it is the proxies that we are all using. I am currently split testing 3 different DC proxy providers and one mobile proxy provider and in the span of the last 7 days, all of the accounts running on the DC proxies have experienced some sort of action block (all of them were follow blocked at a certain moment). On the other hand, not a single account that ran on the mobile proxy experienced any action block.

So, while you can try and resetting the ID, I doubt that you would solve anything with this except risking getting PV or email confirmation. If you truly want to experience smooth actions on your account you would have to consider moving onto Mobile Proxies.

Hope this helps!

Nothing to do with that I have 30 accs affected all running in mobile proxies, it’s related to the API as acs can perform action Via EM

1 Like

We ´re talking about fake follow blocks

1 Like

The past 48/36h a new wave of blocks has started and many had reported this here and elsewhere!! Personally, I got 30 accounts affected all running in 4g proxies ‘‘I don’t run more than 5/proxy at the same time’’
yesterday morning I woke up and all the 30accs are Follow, Like and comment blocked, after some manips I found out that via the EB there is no problem so I asked some folks and been told to reset the device Id, But figured out later that It wasn’t the right move, anyway I reset the Device ID for all the accounts and got about 50% working after that, along the day only 30% are working ‘‘performing actions via API’’ and today most of them can’t perform actions via the API!!

So what’s really going on,?

After some testing, 90% of the accounts can follow and Like via EB using this option:
image
But no comment as we don’t have this option yet in Jarvee!!

I have some old accounts still follow block since the 4th of June but can like and comment via API using Jarvee!! those are running on residential IPs

AND most Important I have other accounts in Datacenter IPV4 that can Follow via API but have some trouble liking and commenting, but here nothing new!!

The Question now Why can’t follow via API in 4g proxy but can do this via Datacenter and residential IPS obviously not 4G!!

Is IG using this metric to fight automation via 4G proxies??

Please tell me if you can relate to this and what do you think?

Thank you to everyone participating here to keep us moving forwar :slight_smile:
Cheers

5 Likes

All of my accounts are on mobile. Still getting random
Blocks.

1 Like

A statement from @DanielAdmin on this would be nice.
I just would like to now if there is a chance to fix those API blocks with a workaround on Jarvee side, as the problem doesn’t seem to have a wrong settings background. It happens randomly and without any parallel to a limit of actions per day or month. In short: What might be a reason for those API Blocks where clients still can perform follows, likes and comments on their phones (also API) when at the same time those interactions are blocked in Jarvee API?

2 Likes

I did reset the ID and tried moving an account that was ok then blocked but way under the 200 I can follow at home no problem on that account, on jarvee just won’t follow, I’m thinking all my proxies are blocked. So anything that got follow action blocked, proxies seem useless. Who’s got good proxies?

1 Like

Yep, so I had cases that following via EB fixed the issue. Now I do still have some accounts encountering issue even tho follow via EB is enabled.

They got another action block the next day. ANy other solution how to fix this would be appreaciated

1 Like

Same here look like 40% of the accs are actions blocked even via EB and of course, 100% are comment blocked!!
Still waiting and observing, maybe an update in the tool will be the solution!!
Let’s hope for the best :sunny:

Y es and above all as I said in the previous comment 40% of the accs are actions blocked!!
And have 7% that can still do actions via API!! Strange han!
Seem really random, as some accs with the more actions are working fine and some accs with less actions are blocked!!
For the proxies and the accs origin’‘creation & utility’’ is the same thing so really really RANDOM mesures…
To be continued…

Same thing for me.
35 out of 200 clients API blocked.
Liking and Following with EB works (besides a few temporary blocks).

And almost all non-client accounts are blocked in like exchange tool but can like manually with EB also :pensive:

2 Likes

Are you doing anything else than liking in the LE with your non-client accounts?
Maybe follows, story views etc.?

1 Like

Its just jarvees api that is effed up. We need to wait for them to fix it…

1 Like

One of the things I saw with my accounts that ultimately were getting api only blocks for likes/follows is I was testing out doing much higher numbers of story views (in the thousands).

So it might be possible the blocks are more api limitations but not actually stating it is an api limitation (since the average person would have no idea what that means). When I shut off story views the following day all the accounts were able to follow/like via api again until they hit their daily limits.

Also API limitations tend to be restricted by IP or device which could very well explain why many of you are affected but your clients have no issues on their phones.

I haven’t done anywhere close to enough testing to say this is definitive. But it is very plausible. So better api call management might be a lot more important now.

At this point I’m not entirely convinced it’s a software specific related issue anymore. Especially since the one deciding factor in any account I had api blocks on what a lot of filters/scraping/story views going on and since I optimized the accounts they’ve run without issue.

8 Likes

Really nice to hear is working fine for you, but personally, I can’t relate as I’m getting this on accs that are not using too much api calls!!
BTW some accs can’t via API BUT can using the EB not in the clients IP & device!!
Thank you for sharing

Really funny to read what I thought about yesterday night. I stopped all scraping actions as good as possible to reduce api calls made by clients accounts. It doesnt seem to be a limit that is being lifted after a short period of time since the accounts are still follow/like blocked now. But I definitely agree with you. The scenario of an API call limitation would make sense, especially for me since I was doing very little interactions in total, but on a high level of quality, which was mainly done through accurate and long scraping sessions. At the same time it would explain why the API block seems to be away after a short period of time when we reset the device ID or if we use the embedded browser. Additionally to all this it would explain why many users are not facing the current issue since they are not doing a massive load of scraping task to filter for HQ sources only.

I’m now hoping and waiting for the limitations to get lifted as it seems to take some time.
I have no idea how many API calls I did, thats the reason why I dont know how long I need to wait over what period of time. But I could imagine that it has something to do with the so called 6000/30 limit. Which might be connected to API calls and not only real actions in some way.

I’ll keep you guys updated on this.

1 Like

@Tacos, this would make perfectly sense.
It’s also what came up to my head at first.
Problems with API Calls --> Solution = Reduce API Calls

BUT sadly it just does not make sense with my affected profiles at all.
I have around 20 API-blocked-clients that only did liking (because they are follow blocked). That should be a minimal amount of scraping. No story Views and No comments, No like comments.
Then a few that did Liking and Story Views only.
Then a few that did Following additionally.
And around 100 that do the same or even use more tools with more strict filters and are working fine.
So for my 35-40 API-blocked-clients at least I cannot see a connection to the amount of API calls done.

But please keep us updated if reducing them works for you.
Thank you @fokus for doing the tests with very limited API calls.
:pray:

.
I would like to share one more thing with you that I think is very very interesting!
Maybe you can help me understand.
I have 19 slave accounts in my like exchange tool.
18 out of those 19 are doing 0 likes in the exchange tool since 2 days. Literally zero. But they are able to like with the EB (I tested for three accounts and made sure with my personal phone that the like sticked).
18 out of 19 API blocked accounts is a crazy high percentage.
And besides the Like Exchange Tool they are very different from each other.
Some of them do following besides the like exchange tool. Some doing Story Views. Some do Following and Story Views. Some to Following, Story Views and Liking Comments. Some do nothing but liking in the exchange tool. On purpose I kept it random so I am able to see connections when problems occur. But I cannot connect this to other tools or API Calls. Also because the Like Exchange Tool should be working just as “like posts of specific users” and therefore need almost no API calls if I am right.

Anyway, now it becomes interesting.
I added 10 more slaves yesterday. They are setup the exact same way as the others. Some do following some were completely paused because they are follow blocked since the 4th.
The only reason they were not in the Like Exchange tool is because there was no need for them to be. I didn’t need the likes at the moment.
Every single one of those 10 account is able to like in the Like Exchange tool.
And the only difference between those 10 and the 19 API blocked is, those 10 did not like anything in the past weeks.

With the data I have it feels like Instagram implemented a program learning tool that detects inauthentic activity and blocks API Calls of the specific device used.
I hope I am wrong…

Maybe they are running on the same proxy?

The question here might be: What were those accounts doing in the past 30 days? Maybe the API call limit doesnt depend on a daily limit, but on an average limit of the last months?

But in total you would say that those 10 accounts were doing much less than the accounts that are like blocked in the LE now during the past 30 days?

Then the question would be: What is inauthentic activity in the eyes of Instagram?
A daily usage of the account with some follow/unfollow below 200 per day each? I don’t think that.