<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pki on Pi Stack</title><link>https://www.pistack.xyz/tags/pki/</link><description>Recent content in Pki on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/pki/index.xml" rel="self" type="application/rss+xml"/><item><title>Complete Guide to Self-Hosted Certificate Management and PKI 2026</title><link>https://www.pistack.xyz/posts/self-hosted-pki-certificate-management-step-ca-caddy-nginx-proxy-manager-2026/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-pki-certificate-management-step-ca-caddy-nginx-proxy-manager-2026/</guid><description>&lt;p>Every self-hosted infrastructure eventually runs into the same problem: TLS certificates. You set up a home lab, deploy a dozen services behind a reverse proxy, and suddenly you are wrestling with expired certs, self-signed warnings, and Let&amp;rsquo;s Encrypt rate limits. If you manage internal services that are not publicly accessible — databases, monitoring dashboards, container registries — public CAs cannot help you at all.&lt;/p></description></item></channel></rss>