Reverse/backdoor proxy

greenleader

Registered Member
Joined
Apr 15, 2013
Messages
71
Reaction score
8
Hi,

I am building a scrape / miner in C# / .NET and have issue with proxy providers where most of IPs are blacklisted for webs I need to scrape.. thus I'd like to build my network of friends/family to run my app. I want it worry free so ideally it'd be backdoor/reverse proxy that connects to main server and waits for instructions - not opening any ports, or fiddling with routers.

is there a commercial solution I could look into or I'd need to build it myself? If you have experience with this, I'm all ears :)
--- ALL LEGAL - with consent.
 
No disrespect mate, but it's a bad idea.
- your scrapes can be blocked because of your code. Test if scraper work on your home IP, if not - proxies are not a problem.
- for mass scraping you need tons of proxies, your solution would not be enough because it would be too small unless you have thousands of friends.
What's most important - keep your scraping solution simple, don't reinvent the wheel. There are good proxy providers on the marketplace, but cheap and good don't exist. You would need to build second brightdata to achieve what you actually want. That's a task for a team of skilled developers - overkill for your scraping needs.

Look for 4g or residential proxy. There is no way around proxies in scraping business, you need a good source of proxies (quality depends on the target website).
If you want in-house proxies you can build something in-house like multiple 4g routers turned into proxies.
 
1. Code works but its downloading thousands of files and target server rate limits it.
2. Dont need thousands of proxies, just under 10 to do sth for 3 hours instead 30. Got multiple tasks like this.

PS: Code implementation and different web work ok.
 
Last edited:
I think even if you set up a proxy using friends' phones, the IPs will still be coming from the Internet Service Provider (ISP), just like with regular proxy providers. The IP could still get flagged over time if it’s used too much or for scraping, since mobile ISP IPs can get blocked or flagged too. But what you're planning is also a solid approach and cost-effective in the long run so best of luck!
 
No disrespect mate, but it's a bad idea.
- your scrapes can be blocked because of your code. Test if scraper work on your home IP, if not - proxies are not a problem.
- for mass scraping you need tons of proxies, your solution would not be enough because it would be too small unless you have thousands of friends.
What's most important - keep your scraping solution simple, don't reinvent the wheel. There are good proxy providers on the marketplace, but cheap and good don't exist. You would need to build second brightdata to achieve what you actually want. That's a task for a team of skilled developers - overkill for your scraping needs.

Look for 4g or residential proxy. There is no way around proxies in scraping business, you need a good source of proxies (quality depends on the target website).
If you want in-house proxies you can build something in-house like multiple 4g routers turned into proxies.
+1 on this. Additionally, consider using rotating mobile/residential proxies to avoid detection and maintain anonymity. These proxies can help reduce the risk of blocks, especially for mass scraping tasks.
 
If you don’t want to fiddle with routers, maybe try using a VPN-based proxy network, you could automate that to get a reverse proxy experience with minimal hassle.
 
If you only need a handful of clean IPs and want zero router work, you don’t need to invent anything exotic. What you’re describing already exists as “reverse tunnels”: Cloudflare Tunnel, Tailscale + SOCKS5, or even Zerotier with a tiny proxy agent on each node. The client machine makes the outbound connection, no ports opened, and you route traffic through it from the main server.

That said, don’t expect this to magically avoid rate limits. From the target’s point of view it’s still residential IPs doing sustained downloads, so pacing, concurrency and fingerprints matter more than where the proxy lives. For <10 nodes it’s workable, but it’s still ops overhead compared to just paying for a few mobile/residential proxies when you actually need them.
 
Instead of building a reverse proxy network through friends' residential connections, you're better off implementing proper request throttling, rotating user agents, and working with premium proxy providers that offer freshly rotated IPs or targeting specific data sources directly through official APIs. Building custom proxy software on other people's machines exposes them to potential IP bans, legal liability, and security risks - even with consent, the technical overhead and reputation damage aren't worth it when legitimate scraping alternatives exist.
 
How do you know they've been blacklisted? I would suggest trying a huge residential pool like 80+ million IP's. A lot of providers these days massively inflate their numbers
 
Back
Top