Every public request to one of my sites used to go through a Cloudflare tunnel. I had a cloudflared deployment in my cluster, some routing rules, and everything just worked. And it was free! But that bugged me. TANSTAAFL right? The whole point of selfhosting is to not rely on big cloud company, and there are few bigger than Cloudflare. And Cloudflare’s tunnels decrypt every single packet, so they see everything you do. I really don’t like that.

So I’ve replaced Cloudflare tunnels with Erwan Leboucher’s towonel, a selfhosted tunnel implementation. I still have my DNS on Cloudflare, but no data is moving through them any more.

  • purplemonkeymad@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 hours ago

    I checked and this does a similar thing. You can use WG to punch out a connection, and I have before. The linked program uses quic in a similar way to WG but doesn’t do any of the routing, just registers the connection to a hostname for application level forwarding.

    It looks more that it provides an easy setup for an alternative.

    Both methods can work on cg-nat as well since you are punching out.