Unsolveable Proxy Issue.

If you’re posting this as a forum thread title, “Unsolveable Proxy Issue” is too vague — and it may reduce the number of helpful replies you get.

People are much more likely to respond when the problem is specific.
 
Advertise on BHW
It could be because you're using a mobile IP but your anti-detect profile looks like a desktop device.

If the IP is from a mobile carrier, try using a mobile fingerprint (Android device, mobile Chrome user-agent, smaller screen resolution, touch enabled, etc.). When the network type and device profile don't match, Google often flags it as unusual activity.

Matching the fingerprint closer to the IP environment sometimes helps reduce captchas.
Jamesjake00121 said:
Hello,

I hope everyone is doing well. I've been using and Setting Up Proxies for some time now and I'm having a reccuring Issue which i cannot Seem to Solve.

Some Background:

1. Using An Android To Rotate My IP.
2. Used Different Mobile Carriers.
3. Used Different Softwares. (IPproxy + Proxodize)
4. Used Different Anti-Detect Browsers (Incognition + Multi-Login)

I installed IPproxy and Used Tello (A Mobile Carrier). I input all the information as asked on the Anti-detect Browser, and then get hit with ; "Google Has Detected Unusual Activity"

So I have talked to many people Here on the fourm and they said, its probably your carrier. So, I Switched To T-Mobile. Did The Same exact thing. Still, The same issue persists.

I then thought IPproxy was the issue so I have switched to Proxodize and The same issue again. I Must make it clear, when I use the Anti-detect browser by itself, no issue. When I use the Proxy by itself (on the android) VIA Proxodize, No issue. The moment I put the two together I get this issue of needing to solve 100 captchas.

I have also run HTTP + Normal Web (No Anti-detect) + Proxy on The Proxodize Extension and I did not have any issue.

Does anyone have any idea?

Many Thanks.
Click to expand...
 
Sounds like a fingerprint mismatch between the anti-detect profile and the mobile proxy. When things like timezone, user agent, or WebRTC don’t match the IP, Google flags it and throws captchas. Try making the browser profile match the proxy exactly.
 
It’s not the carrier, proxy app, or antidetect itself. It’s how they look together.

Right now you’re sending a mobile IP, but the browser fingerprint still doesn’t fully behave like a real phone. Even if you matched OS and timezone, things like WebGL, canvas, WebRTC, or even small inconsistencies in device specs can give it away.

That’s why each part works alone, but combined it trips Google.

I’d focus on:
  • making the profile look like a real Android device (not just “Android OS” preset)
  • double checking for any IP/DNS/WebRTC leaks
  • making sure the IP location matches down to city level, not just country
Also worth testing your profile on browserleaks before using it, you’ll usually spot what’s off pretty quickly.
When you test on browserleaks, does everything actually match the proxy IP or do you still see your real machine showing up somewhere?
 
Honestly looks like a classic mobile IP + desktop fingerprint mismatch.

The proxy itself is probably fine — that’s why it works in normal browser and even in anti-detect alone. But when you combine mobile carrier IP + desktop-style fingerprint (canvas/WebGL/device specs), Google sees it as inconsistent and starts throwing captchas.

Seen this happen a lot with phone proxies. Try making the profile look closer to a real Android device (mobile UA, screen size, WebGL, etc.) instead of a desktop profile behind a mobile IP.
 
It sounds like google sniffs out the whole combo when that anti-detect browser and proxy link up, even if they chill by themselves. Probably something in that joint setup still screaming about to their algorithms
 
Sounds like a fingerprint mismatch tbh. The proxy + anti-detect combo is probably throwing Google off. Maybe you should try matching your profile to mobile better or run a clean profile.
 
I suspect the issue stems from a mismatch between the browser fingerprint and the IP environment—each works fine on its own, but when combined, they don’t appear to be from a real user, triggering the risk control measures.
 
It's probably google flagging the combo of your specific anti-detect browser profile and that mobile proxy ip as sketch, even if they're fine solo. Google's bots are just wild like that, maybe try a different anti-detect browser or really dive into customizing the fingerprint settings more aggressively
 
Bro, sounds like Google's just super good at sniffing out anti-detect browsers trying to look legit through a proxy, even with a clean mobile IP. It's probably less about the proxy or carrier being 'bad' and more about the combo making your footprint look too perfect or suspiciously inconsistent to google's advanced bot detection
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top