Proxies are dying for Instagram / Facebook

immensity

Newbie
Joined
Oct 3, 2022
Messages
17
Reaction score
6
Hey all, I wanted to bring bad news for those who automate Instagram. They have for a month or two now quietly added in updates to support QUIC / HTTP3. I do not believe many people across the world have noticed this change.

If you use the API you will notice increased bans despite doing normal and low actions (read 10 follows) as of recent.

For those of you that do not know why HTTP3 is relevant:

https://www.blackhatworld.com/seo/proxies-will-die-in-2023.1448749/

The solutions listed in that that video do not work, because if you use HTTP2 traffic IG thinks something is wrong with the account.

Since Instagram is app based, they control the SSL library, they can do whatever they want and know for sure a normal request should act like x, y, z, instead of a, b, c.

It is normal that some requests will land as HTTP2, so IG doesn't instant ban you. Your account is flagged if you get too many however.

You can confirm my words with https://github.com/Eltion/Instagram-SSL-Pinning-Bypass/issues/19

Though they only noticed later on, and do not realize the implications of HTTP3. Disabling HTTP3 will not help.

At current, it seems not any of the big proxy providers support UDP through socks5. Proxidize is not a solution either. @BetterKnow, if you can add UDP support people will pay.
 
Hi,
1. "they" = instagram?
2. if I give you a proxy that supports QUIC\HTTP3, what is the tool you will be using for QUIC\HTTP3? In my thread I mentioned, there are no client tools for QUIC\HTTP3.
3, Use VPN, it doesn't have this issue.
 
Hey all, I wanted to bring bad news for those who automate Instagram. They have for a month or two now quietly added in updates to support QUIC / HTTP3. I do not believe many people across the world have noticed this change.

If you use the API you will notice increased bans despite doing normal and low actions (read 10 follows) as of recent.

For those of you that do not know why HTTP3 is relevant:

https://www.blackhatworld.com/seo/proxies-will-die-in-2023.1448749/

The solutions listed in that that video do not work, because if you use HTTP2 traffic IG thinks something is wrong with the account.

Since Instagram is app based, they control the SSL library, they can do whatever they want and know for sure a normal request should act like x, y, z, instead of a, b, c.

It is normal that some requests will land as HTTP2, so IG doesn't instant ban you. Your account is flagged if you get too many however.

You can confirm my words with https://github.com/Eltion/Instagram-SSL-Pinning-Bypass/issues/19

Though they only noticed later on, and do not realize the implications of HTTP3. Disabling HTTP3 will not help.

At current, it seems not any of the big proxy providers support UDP through socks5. Proxidize is not a solution either. @BetterKnow, if you can add UDP support people will pay.
I mean it’s something that I would not understand why they didn’t have in the first place.
But in a few months UDP will be possibly available at many places so just need to wait.
 
Hi,
1. "they" = instagram?
2. if I give you a proxy that supports QUIC\HTTP3, what is the tool you will be using for QUIC\HTTP3? In my thread I mentioned, there are no client tools for QUIC\HTTP3.
3, Use VPN, it doesn't have this issue.

1. By they I mean the people in the GitHub issue.
2. This is another problem, though it seems useless to work on it without being able to proxy QUIC. I use Proxidize through @BetterKnow, who mentions it's easy to support it. So maybe I will have a chance soon.
What I guess may have to happen is you will have to intercept requests, and maybe then you can mimic a normal request, or you would have to decompile the app, and try and figure it out from looking at their custom SSL / networking library. All of which is a huge pain. Potentially there are more ways to do it, though I haven't done the research necessary while figuring out the proxy situation.
3. That's cool. It does have the problem of only being 1 connection however.

This implies that even manual growth on phones is impacted now, unless you are giving every phone it's own sim card and data plan
 
i remember 10/15 years ago pretty much anything worked on SM
but as SM and proxies took off and users made millions of accounts

usually for spam. the effectiveness of proxies dropped over time.
they still work, just no in greater numbers as b5
 
I mean, they have at this point years of experience. Congrats to their engineers honestly
 
I have been working on new version of the script for registration Instagram accounts with my proxies and I've found success in it. The code is still in beta, but yeah, the registration worked out for me
 
Registration works fine, problem is with certain actions you do on the account.

I am also unsure if account trust score is lowered, though potentially that hits too many users.
 
Back
Top