Yes in zero trust > access controls > applications you can specify a web site and then tell it how you want it protected. In its most basic form you can have it email you a login code, but if you link it to either google or Microsoft you can have users of those services use them allowing you to sso straight through.

You can also specify a wildcard *.mydomain.net and then by default anything that is in your domain will be protected. Means when you’re testing something new you won’t forget to lock it down.

You’re correct about media, I use nginx proxy manager for emby, but everything else goes through the tunnels

As for configuring, the cloudflare LLM bot has been trained on all its documentation so it’s one of the few times a chat bot is genuinely useful.

Cloudflare tunnels is a great way to expose services on your network to the web.

You run a program in your server, it makes a tunnel, then you configure it on the website to visit the internal link in your network, eg

If you’re hosting a web server at home, you could have something like:

www.mydomain.net > http://192.168.1.55:8080/

You can also have cloudflare protect access to that website with email verification, google / Microsoft accounts etc.

It’s a lot to learn, but it’s very handy once you get the hang of it.

Here’s a YouTube video on the basics: https://youtu.be/Q5dG8g4-Sx0?is=J7KvNZoyjsEq33fO