Comment on Question about traffic using Cloudflare tunnel
sk@utsukta.org 3 weeks ago
yes, its also called hairpinning. to avoid this you can use a local dns resolver.
Comment on Question about traffic using Cloudflare tunnel
sk@utsukta.org 3 weeks ago
aksdb@lemmy.world 3 weeks ago
Cloudflare tunnel likely terminates TLS on the edge. So if you bypass it, you don’t have HTTPS. Not a problem locally, but then destroys the portability of the URL (because at home you need http and outside you need https). Might as well use different hosts then.
AmbiguousProps@lemmy.today 3 weeks ago
You can use caddy to get internal https via cloudflare API, and no traffic needs to go through a cloudflare tunnel for that.
aksdb@lemmy.world 3 weeks ago
Possible, true. But then the setup also becomes more complicated. In addition you end up with different certs for local and remote access, which could cause issues with clients if they try to enforce cert pinning for example.
AmbiguousProps@lemmy.today 3 weeks ago
The (wildcard) certs are the same, as it’s what caddy is pulling via API. You can either build the cloudflare module into caddy via docker build, or use a prebuilt version. It doesn’t create two separate certs for local and remote.
It works really well for me, and is actually the most straight forward way to get valid certs for internal services I’ve found. Since they’re wildcard, my internal domains don’t get exposed through certificate authorities.