Cloudflare tunnel limitations with HTTPS terminating

Recently, I was setting up public hostnames over a Cloudflare tunnel to access services within my homelab.

It behaves as a simple proxy. However, I haven’t been able to set up HTTPS terminating on Cloudflare’s end. This essentially means that if my local services are not configured for TLS internally, then there is no TLS publicly either.

I’m not saying this is a bad thing; just a very human oversight on my part regarding how Certificates play a role in this alongside Routes and Targets. I need to look into this more. I hope this helps.