<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Websocket - Tag - Lorenzo's Blog</title><link>https://www.k8s.it/tags/websocket/</link><description>Websocket - Tag - Lorenzo's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 03 Aug 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.k8s.it/tags/websocket/" rel="self" type="application/rss+xml"/><item><title>Websocket, Cloudflare Tunnel, Apache httpd and a Bit of Security</title><link>https://www.k8s.it/posts/websocket-cloudflare-tunnel-apache-and-irritation/</link><pubDate>Thu, 03 Aug 2023 00:00:00 +0000</pubDate><author>Lorenzo Girardi</author><guid>https://www.k8s.it/posts/websocket-cloudflare-tunnel-apache-and-irritation/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/websocket-cloudflare-tunnel-apache-and-irritation/Screenshot-2025-04-26-at-00.35.02.png" referrerpolicy="no-referrer">
            </div><h2 id="the-infrastructure-overview">The Infrastructure Overview</h2>
<p>Exposing home lab services to the internet can be both necessary and risky. Traditional methods — port forwarding, VPNs, reverse proxies with open inbound ports — come with their own set of challenges. This is where Cloudflare Tunnel (formerly Argo Tunnel) comes in as an elegant solution.</p>
<p>In this article, I&rsquo;ll walk you through how I&rsquo;ve implemented a secure infrastructure using Cloudflare Tunnel with WebSocket support, running on a Kubernetes cluster with Apache HTTPD as a reverse proxy. This setup allows me to securely expose internal services without opening ports on my residential firewall.</p>]]></description></item></channel></rss>