# Cloudflare's 2nd greatest gift to humanity - WARP

**URL:** <https://mpsocial.com/t/cloudflares-2nd-greatest-gift-to-humanity-warp/160353>\
**Category:** Tools of the trade\
**Created:** [January 30, 2025, 3:57am UTC](https://mpsocial.com/t/cloudflares-2nd-greatest-gift-to-humanity-warp/160353 "2025-01-30T03:57:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Legitsms](https://mpsocial.com/user_avatar/mpsocial.com/legitsms/32/74506_2.png) [@Legitsms](https://mpsocial.com/u/Legitsms)\
**Post date:** [January 30, 2025, 3:57am UTC](https://mpsocial.com/t/cloudflares-2nd-greatest-gift-to-humanity-warp/160353/1 "2025-01-30T03:57:12Z")

</div>

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/](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…

---

<div class="post-metadata">

**Author:** ![darius7](https://mpsocial.com/user_avatar/mpsocial.com/darius7/32/74907_2.png) [@darius7](https://mpsocial.com/u/darius7)\
**Post date:** [September 3, 2026, 10:31pm UTC](https://mpsocial.com/t/cloudflares-2nd-greatest-gift-to-humanity-warp/160353/2 "2026-09-03T22:31:10Z")

</div>

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.