Self proxy issue

crazygringo77

Newbie
Joined
May 10, 2026
Messages
5
Reaction score
0
Hello. Some time ago I started to make self android proxies and everything worked smooth. As soon as I increased quantity of phones I encountered a problem where sometimes I can't pass captcha or pay for something, however other pages still work. I wonder if its problem of signal or something else ? Any advices? speed is 10-20mbps
On photo you can see that page is working, but captcha not . Same with 3ds payments
Screenshot 2026-05-09 231530.png
 
If captcha is broken, problem is in proxy software or in antidetect. I’d say 90% it’s in software.

Stuff happens, all the way to things like TLS 1.3 not working but 1.2 does, for example. We’ve seen that. You need to debug: look at which URLs are being sent, look in browser dev console why it’s not opening. Only debugging will show you the cause.

Were captchas broken before scaling? Maybe before scaling they didn’t pop up at all and scaling raised your behavioral flags? Then work on not triggering captcha in the first place.
 
If captcha is broken, problem is in proxy software or in antidetect. I’d say 90% it’s in software.

Stuff happens, all the way to things like TLS 1.3 not working but 1.2 does, for example. We’ve seen that. You need to debug: look at which URLs are being sent, look in browser dev console why it’s not opening. Only debugging will show you the cause.

Were captchas broken before scaling? Maybe before scaling they didn’t pop up at all and scaling raised your behavioral flags? Then work on not triggering captcha in the first place.
It's not only about captchas, but about the payment gateways which i used very often to pay for goods and now they are broke too. I'm using localtonet atm, since I can't afford your service :D
 
sounds more like a ip quality/session consistency rather than raw speed. if too many devices are in the same carrier pool or the ip changed mid-session the captcha may keep failing. your rotation cannot be too aggressive especialy for payments. u have to use the same ip. the speed isnt the issue
 
Doesn’t really sound to me like a purely stability issue if normal pages still load alight. Captchas and 3DS flows are usually a lot stricter with browser/device integrity and network checks, so yeah, I'd also lean on a software or setup related issue.
 
Point above about IP rotation is very good. If your rotation is more often than every couple min, or even less than a min, problem will be exactly in this. But if rotation is less frequent, say every 3-5 min or more, this would already lead to not every captcha/3ds being broken.

And yes, captchas and 3ds are most likely showing the same problem.

I’m curious myself how our software would behave in your setup. If you’re interested, dm me, I’ll give you a free extended period to check it.
 
Hello. Some time ago I started to make self android proxies and everything worked smooth. As soon as I increased quantity of phones I encountered a problem where sometimes I can't pass captcha or pay for something, however other pages still work. I wonder if its problem of signal or something else ? Any advices? speed is 10-20mbps
On photo you can see that page is working, but captcha not . Same with 3ds payments
View attachment 522492
At a 2-week rotation, it’s unlikely the issue is the rotation itself. If normal browsing works but captcha and 3DS payments fail, it’s usually tied to IP reputation or browser/device fingerprint consistency.

You might want to test:
  • Keeping each session fully consistent (same browser profile, stable fingerprint, no mixing environments or devices per session)
  • Avoiding frequent changes in timezone, WebRTC, or browser settings within the same identity
  • Testing with a clean browser profile (no extensions) to rule out local interference
  • Ensuring you’re not reusing sessions across different device setups unintentionally
Let me know if that helps or if the issue improved after testing.
 
I just made my own setup with tailscale + everyproxy and it fixed the problem
 
I just made my own setup with tailscale + everyproxy and it fixed the problem
Self-hosted setups often work better because the routing stays cleaner and more consistent. Captcha/3DS systems care more about session integrity and fingerprints than raw speed. Nice find.
 
Back
Top