<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Step-Ca on Tod's Homelab</title><link>https://homelab.tod.net/tags/step-ca/</link><description>Recent content in Step-Ca on Tod's Homelab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 29 Jun 2026 12:00:00 -0400</lastBuildDate><atom:link href="https://homelab.tod.net/tags/step-ca/feed.xml" rel="self" type="application/rss+xml"/><item><title>The PKI Detour: A Week on the Wrong Cert Strategy, Three FreeIPA Failures</title><link>https://homelab.tod.net/posts/downsizing-the-homelab/the-pki-detour/</link><pubDate>Mon, 29 Jun 2026 12:00:00 -0400</pubDate><guid>https://homelab.tod.net/posts/downsizing-the-homelab/the-pki-detour/</guid><description>&lt;p&gt;&lt;a href="https://homelab.tod.net/posts/downsizing-the-homelab/infrastructure-to-build-infrastructure/"&gt;GitLab was up&lt;/a&gt;. The code had a home. The obvious next question was: how does every other internal service get a TLS certificate?&lt;/p&gt;
&lt;p&gt;The answer I wanted: something clean, automated, and not requiring full Cloudflare DNS credentials on every host. The answer I got — eventually — was &amp;ldquo;Cloudflare DNS-01, one token per service, and accept the limitations.&amp;rdquo; Getting there took a week on the wrong approach, then six days and three attempts on a more ambitious one. This post is both of those failures, what they cost, and what survived them.&lt;/p&gt;</description></item></channel></rss>