Cloudflare's 2nd greatest gift to humanity - WARP

Tools of the trade
1

In my never-ending quest for a great residential proxy, I have (recently) come across Cloudflare WARP and nearly instantly realized - it will save me, my business and will help (maybe dozens?) who read this thread… Anyways, here it is - WARP - Cloudflare’s biggest gift to humanity (and personally me), probably nearly as big as their free DDOS protection. If you are not familiar with WARP - check this out https://one.one.one.one/ and for me most important is the recently added Linux support. Are you already seeing where I am going with this? After a bit of research and a little bit of trial and error, I was able to create for myself super awesome, Cloudflare “hosted” proxies with virtually unlimited bandwidth and quite possibly a pool of 1,5m IPs at hand… WOW WARP, JUST WOW… started with a few proxies across the globe, will make quite a few more… All one needs is a VPS and with a bit of practice, can deploy proxy in the desired geo in 15-20 minutes (5-10 if you know your stuff)…

And just like that WARP masks your VPS’s IP and acts like a proxy with rotating outgoing IPs, both IPv4 and IPv6… Only need to install 2 apps on the server - warp-cli and dante-server (socks). That’s it!! How crazy is that??? … The only thing, I haven;t been able to make nginx work right with WARP, it seems you need to host DNS on Cloudflare and do a tunnel for nginx to work with WARP, that’s a bit of extra work…

1 Like
2

Cloudflare WARP changes the VPS-to-internet egress path; it is not a conventional residential-proxy pool. Traffic may exit through shared Cloudflare addresses, but per-request rotation and geographic selection are not guaranteed, so those addresses should not be modeled as 1.5 million dedicated residential IPs.

nginx is the opposite direction: internet-to-VPS ingress. WARP’s outbound tunnel does not publish the VPS or make nginx reachable through Cloudflare. That requires a separate inbound design: proxied DNS to a reachable origin where appropriate, or a Cloudflare Tunnel when the origin should remain behind the outbound connection. DNS alone does not create that path; the ingress state must be explicitly configured.