I finally understand Cloudflare Zero Trust tunnels

(david.coffee)

311 points eustoria | 1 comments | 16 Nov 25 17:39 UTC | HN request time: 0.203s | source

Show context

plantinthebok ◴[16 Nov 25 19:52 UTC] No.45947870[source]▶

What's the actual win here? Avoiding relay latency in the rare cases Tailscale can't punch through NAT? If that's it, a $3 VPS running Headscale seems simpler. The complexity feels like you're optimizing for the 5% case while adding permanent vendor lock in. What am I missing?

replies(6): >>45947999 #>>45948012 #>>45948016 #>>45948087 #>>45948806 #>>45952600 #

killingtime74 ◴[16 Nov 25 20:12 UTC] No.45948016[source]▶

>>45947870 #

For many homelabbers, just being cheap and avoiding the $3 VPS, that's it

replies(2): >>45948073 #>>45950265 #

1. anon7000 ◴[17 Nov 25 02:06 UTC] No.45950265[source]▶

>>45948016 #

Exactly, just today I set up a cloudflare tunnel to a docker compose service running on my home server. I didn’t want to expose the server directly to the internet, and I want to share this service on a certain domain with broader family.

I have a server at home that works well. I don’t reaaaally want to pay an extra $30-$40/yr and have an extra thing to manage when the CF tunnel works fine for free. I like Tailscale more, but I want to share this with family who won’t install TS and also want to use a specific domain.

↑