[m-app]

Regarding your second point: When I initially configured my Cloudflare Tunnels + Access setup, I spent way too much time getting the App Launcher [0] nice and pretty. Seemed really useful seeing as I came from a setup with VPNs and internal IPs, but did not realize that because Cloudflare Access gives you free pretty URLs, I would never look at it again…

0: https://developers.cloudflare.com/cloudflare-one/application...

[tra3]

That’s really neat. I want to expose some self hosted services externally. Is this a good option? I see that there’s a free plan. How’s it working for you?

[vladvasiliu]

I'm also doing this and I like it.

One of the most useful things for my case is the access control. Basically, I want my services to be accessible from anywhere, but only by me. This allows me set up authentication before the requests even hit my server.

If you want your services to be world accessible, that works well, too. They even have an agent that initiates the connection from the server, so it works well behind ISP CG-NAT, dynamic IPs, etc, and you don't have to mess around with incoming connection filtering.

[tra3]

This is really cool. So I just exposed an instance of next cloud, but it requires an email verification before being accessible. Super cool.

Is the cloudflared smart enough to route connections locally? Hm, not sure how that would work.

I'm sitting at home, but accessing my nextcloud through the cloud flare. Is there a way to get it to talk to nextcloud locally or is it going through the net?

[vladvasiliu]

> Is the cloudflared smart enough to route connections locally? Hm, not sure how that would work.

Do you mean have cloudflared expose your local server locally? No. It's just a reverse proxy of sorts between cloudflare's network and your local server.

What you want can be achieved with local DNS, so that nc.tra3.com resolves to <cloudflare-ip> from outside and to 192.168.1.2 from inside. But you should probably also have a local certificate for this to be fully transparent.