So everyone is talking about cloudflare tunnels and I decided to give it a shot.

However, I find the learning curve quite hard and would really appreciate a short introduction into how they work and how do I set them up…

In my current infrastructure I am running a reverse proxy with SSL and Authentik, but nothing is exposed outside. I access my network via a VPN but would like to try out and consider CF. Might be easier for the family.

How does authentication work? Is it really a secure way to expose internal services?

Thanks!

2 points

People are saying that it is a cloud managed reverse proxy, but I would not recommend using it like this. You should be running a reverse proxy on your own hardware, imo.

It is still useful because you can use it as just a proxy. You can point your dns to your cloudflare tunnel endpoint and cloudflare will screen all traffic going to your server. I’ve actually stopped using it, but it is a decent way to auto feel all the random internet traffic pitfalls like portscanning bonnets. Also putting something between your server IP and your domain is nice.

permalink
report
reply
1 point

Basically just an easier way to get a tunnel into your server, instead of having to configure a reverse proxy or manage certs. I just have the cloud flared docker installed, then on their site under the tunnels section I just assign whatever domains or subdomains to all my services via a local ip address. Im doing a couple things that definitely break TOS lol. But imma let it ride till they stop me then I guess I’ll switch to a reverse proxy

permalink
report
reply
1 point
*

I used one to reach my qbittorrent selfhost. I found a cool docker image. It bundles a openVPN connection with qbittorrent so that I don’t need my home server to be on a VPN at all times. As well as ensures traffic always goes through VPN. I was running into an issue where I could not reach from my home network. But when I used a cloudflare tunnel it somehow worked. This was all until I realized there was an environment variable of LAN I needed to set which allowed connections from my home network 😮‍💨

I would definitely recommend this setup for any torrenting. I’ve been using it for years with zero IP leaks. Believe me, Spectrum would let me know. They did before I had setup.

EDIT: just realized the guy deleted the docker image for that based on a false positive (that’s been a false positive for a year). I reuploaded their same image to my docker account. Still works without any leak, not sure why they took such a drastic measure.

permalink
report
reply
1 point
*

What I’m doing is using a dedicated VPN Gateway container. The instances running delicate services have a static default route to the GW-container.

This is an extra step, but allows me add easily route other services or clients or even whole networks through my VPN without additional setup or specialized containers bundling both.

Wanna use it on the phone? Change the gateway address. Wanna use it from my Linux machine? Add a static default route. Etc…

Works flawlessly!

permalink
report
parent
reply
2 points

That sounds better since it doesn’t have any kind of bundling of images. Do you have a link to anything public I can look at to try out a similar setup?

permalink
report
parent
reply
1 point
*

Unfortunately not at the moment, as all is kinda fiddled and setup manually, but I’m redoing my home lab in a couple of weeks. Send me a message and I’ll send you the docker image or script!

But basically I did the following:

  • enable ipv4 forwarding
  • configure and start VPN tunnel
  • set the default route to the tunnel
  • set the gw for reaching the remote vpn server to the local gw
  • sets routes for the local network to the local gw

If your vpn goes down, the default route shall still point to the remote gw, but as it isn’t there you also have a kill switch. Voila!

I am looking into gluetun but haven’t tried it yet.

Edit: this doesn’t protect you from someone snooping the traffic inside your local net, but protects it starting from the point where it leaves the local vpngw. The traffic is unencrypted between that and your client.

permalink
report
parent
reply
3 points

@operator

Cloudflared tunnels are great. No firewall ports to open.

I installed the Cloudflared docker, which is headless, and fed it my API key. Then Cloudflared creates a VPN between your system and theirs. Then, think of Cloudflare as the reverse proxy, you just configure it on the CF site instead of locally. No need for a reverse proxy on your side.

I’ve not done anything with auth on it as what I run I don’t mind being public. If you still want to run a local auth, you can set it to hit your local reverse proxy instead and do it that way.

The benefits are you don’t need to open firewall ports and your local IP is irrelevant so no need for dynamic DNS.

permalink
report
reply
3 points

Just a side note that “not opening firewall ports” is not inherently a security benefit if you’re exposing the same service on the same port on the same host anyway via your reverse proxy setup.

If you were to measure your level of “security” on having ports open or not alone, then using Cloudflare tunnels could be considered worse, since an outbound VPN connection to Cloudflare is essentially circumventing your firewall’s protection entirely, meaning you’re effectively opening all 65,535 TCP and UDP ports instead of one, albeit only to Cloudflare.

There are benefits to using Cloudflare tunnels but “not opening firewall ports” is not one of them. And you could just as easily accomplish the same thing without Cloudflare by using a VPS and Tailscale with the selfhosted Headscale coordinator.

permalink
report
parent
reply
1 point

Meh, it’s sorta 6 of one and half-dozen of another. The benefit of not opening ports on a firewall isn’t necessarily a security one so much of a convenience one for people who don’t know how their routers work or no access to open those ports. The only security value is it prevents any exploits on your router and a port scan against your network won’t show those ports open. That makes it easier to hide the fact that your hosting something. I’d agree, it’s not a huge security vector to worry about, but can help people not see your real IP which has tangible value.

Really, your offloading security to CF and putting trust in them to do a better job than you, but as you said, in doing so they can sort of get the keys to your kingdom. I think it’s just worth it with their other tools to block bots and other common exploits that a Netgear home router isn’t looking for.

The problem with a vps and tailscale is its one more thing to manage and a vps costs money and cf is free.

permalink
report
parent
reply
6 points

I know some people dislike NetworkChuck but this video should help you get things going.

https://youtu.be/ey4u7OUAF3c

permalink
report
reply
1 point

I don’t get the hate.

permalink
report
parent
reply
1 point

No I don’t. I get he isn’t to everyone’s taste but his videos I think are enjoyable because he obviously has enthusiasm and I e set up a home lab running proxmox, a load balancer, monitoring software and a heap of other stuff because of him.

permalink
report
parent
reply
4 points

NetworkChuck does videos for beginners, but sometimes that’s just what an experienced user need ^^ thanks for sharing! Watching the video right now

permalink
report
parent
reply
9 points

Here is an alternative Piped link(s): https://piped.video/ey4u7OUAF3c

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I’m open-source, check me out at GitHub.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments