<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Traefik on Blaž Škufca</title><link>https://blazskufca.com/tags/traefik/</link><description>Recent content in Traefik on Blaž Škufca</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blazskufca.com/tags/traefik/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-hosting with pfSense, Cloudflare, Traefik, CrowdSec and Docker</title><link>https://blazskufca.com/projects/selfhosting-with-pfsense-and-docker/</link><pubDate>Sat, 17 Jan 2026 00:00:00 +0000</pubDate><guid>https://blazskufca.com/projects/selfhosting-with-pfsense-and-docker/</guid><description>&lt;p&gt;Self-hosting gives you complete ownership of your data, but exposing services to the internet requires a security-first mindset. This project details my approach to building a secure, scalable self-hosting stack. By combining the routing power of pfSense, the edge protection of Cloudflare, the community-driven defense of CrowdSec, and the flexibility of Docker, I&amp;rsquo;ve created an environment that balances accessibility with hardened security.&lt;/p&gt;
&lt;h1 id="configuring-pfsense"&gt;Configuring pfSense&lt;/h1&gt;
&lt;h2 id="network-segmentation"&gt;Network Segmentation&lt;/h2&gt;
&lt;p&gt;Security starts with isolation. I use pfSense to create a separate VLAN for my self-hosted services, ensuring that even if a container is compromised, it cannot access my main LAN or administrative interfaces.&lt;/p&gt;</description></item></channel></rss>