Why doesn't WARP IP rotation work on Hugging Face / Koyeb?
On the free WARP tier, the egress IP is decided by Cloudflare from two things:
- the Cloudflare colo closest to your source IP (HF Spaces → IAD, Koyeb EU → FRA);
- a small shared NAT pool inside that colo.
On a VPS your source IP is unique, so each new wgcf identity lands in a different session of the pool → different egress IP. Rotation works.
On Hugging Face / Koyeb the source IP is the datacenter NAT shared by thousands of containers. Cloudflare pins you to the same 1–2 IPs in the local colo no matter how many times you regenerate the wgcf identity or rotate the MASQUE endpoint. This is a free-tier limitation, not a bug of this addon.
What this container already does (max possible on free): new wgcf identity every boot, IPv4-only profile, optional MASQUE endpoint pick (WARP_ROTATE=1).
What works on free + managed platforms: when uprot/clicka start blocking the WARP IP, the badge above turns red after ~22h. Do a Factory reboot (HF) or Redeploy (Koyeb) — sometimes the new container lands on a different host with a different IP. Then re-solve the captcha at /chapta.
Real egress rotation on managed platforms requires WARP+ / Zero Trust (paid, per-account device token) or a paid residential proxy. Neither is shipped here because this is a free self-host addon — no personal keys.