Secure Web Apps with Cloudflare Tunnels
Вставка
- Опубліковано 11 вер 2024
- Hey friends! Quick video on how to use Cloudflare tunnel to secure any web application, WITHOUT the fuzz of setting up HTTP servers, installing certificates, etc.
🙌 Get in Touch
Join my newsletter and say hi at axgr.dev/newsl...
🎙 Gear & Links
Mechanical Keyboard: x.axgr.dev/key...
Studio Camera: x.axgr.dev/stu...
Studio Lens: x.axgr.dev/stu...
Studio Mic: x.axgr.dev/stu...
Vlog Camera: x.axgr.dev/vlo...
Vlog Lens: x.axgr.dev/vlo...
All my affiliate links axgr.dev/deals...
I may earn a small commission for purchases made through the links above at no additional cost to you.
🍿 Subscribe if you want to see more tech videos + tutorials!
🤑 Use the link below to get a $100, 60-day credit for Linode
x.axgr.dev/linode - or check additional deals at axgr.dev/deals...
Thanks for the video :)
Thanks for watching!
Hi Alex - thanks for making this video.
I'm struggling to understand the security advantages of using Cloudflare Tunnel in a situation like this (server with a public IP), and to a lesser extent in a situation where the service is hosted in a local network.
If the service is on a cloud server which already has a public IP address, is there any real security gain in sending clients through a Cloudflare Tunnel?
If the service is in a private network but the tunnel makes it available on the internet, is it not just as available as it would be if it were sitting on a public IP, and therefore vulnerable to the same attacks?
Hey there, great questions! For the public server, using CF tunnels does not require you to expose any ports at all. The alternative is using something like Let's Encrypt which requires you to open ports 80 (HTTP) and 443 (HTTPS) on the machine and also manage certificate renewal. With the tunnel, your server doesn't have to expose any of these ports. Plus, all traffic is routed through Cloudflare, which scans for known vulnerabilities and attacks. It can also shut down access to the machine if it detects any malicious patterns, or require additional authentication (username + password, Google Login, ..) This is a feature that you would have to build yourself as well.
As for the private server, it is mostly the same thing. You don't expose the network per-se to the internet. If you run a cluster of Docker containers then you can configure the Cloudflare container to only have access to a specific container and port. So the requests don't even have access to the Docker host machines, or other servers in your network (unless you want to). Does that answer your questions?