this post was submitted on 23 Dec 2025
73 points (94.0% liked)

Selfhosted

53934 readers
348 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm using CloudFlare to hide my home IP and to reduce traffic from clankers. However, I'm using the free tier, so how am I the product? What am I sacrificing? Is there another way to do the above without selling my digital soul?

you are viewing a single comment's thread
view the rest of the comments
[–] irmadlad@lemmy.world 5 points 3 days ago (1 children)

I’m an expert at nothing, however, the following is how I understand the relationship between your origin server and Cloudflare Tunnels/Zero Trust services. I stand by to be schooled:

  • Traffic between your origin server and Cloudflare’s edge is always encrypted (with outbound only connections via cloudflared daemon). That protects against eaves dropping on the wire between your origin server and Cloudflare.
  • Traffic between end users/clients and Cloudflare’s edge is encrypted (via HTTPS/TLS).
  • However, Cloidflare acts as a proxy, similar to a reverse proxy. For standard HTTP/HTTPS services. Cloudflare terminates TLS decrypts at their edge to apply features like WAF, DDoS protection, caching, or Zero Trust policies. They then reencrypt and forward the traffic to your origin server. This means Cloudflare can see the plaintext content of your traffic in transit through their network.
  • If you expose non-HTTP protocols that are end 2 end encrypted by design (e.g., SSH, RDP, or VPN protocols like WG/OVPN), and you tunnel them thru Cloudflare Tunnel without Cloudflare terminating the encryption, the application slayer data remains encrypted end 2 end. Cloudflare only sees encrypted blobs which they can’t decrypt without the keys.
  • Utilizing Tailscale on the origin server creates a mesh VPN using WG. It encryps all traffic directly between devices. P2P when possible, or encrypted relays. Your data is encrypted on the source device and only decrypted on the destination device. Neither Tailscale’s coordination servers nor Cloudflare can decrypt it.

If this is inaccurate, please do EILI5. I’m always down to learn.

[–] boonhet@sopuli.xyz 2 points 3 days ago (1 children)

Pretty sure you can choose to decrypt on your own server so cloudflare doesn't see unencrypted data ever.

[–] irmadlad@lemmy.world 3 points 3 days ago

Indeed you can. When a user makes a request, it is sent to Cloudflare, which then routes it to your server through the tunnel. The traffic can be encrypted while in transit to Cloudflare, ensuring that their network does not inspect or decrypt the contents. Once the encrypted traffic reaches your server, you handle decryption using your own application logic. Only your server has the keys to decrypt the data, so Cloudflare remains blind to any sensitive information.