<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tls on Pi Stack</title><link>https://www.pistack.xyz/tags/tls/</link><description>Recent content in Tls on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>Best Self-Hosted TLS Termination Proxy: Traefik vs Caddy vs HAProxy (2026)</title><link>https://www.pistack.xyz/posts/self-hosted-tls-termination-proxy-traefik-caddy-haproxy-guide-2026/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-tls-termination-proxy-traefik-caddy-haproxy-guide-2026/</guid><description>&lt;p>A TLS termination proxy sits at the edge of your network, handling HTTPS decryption so your backend services don&amp;rsquo;t have to. It manages SSL certificates, enforces TLS versions, and offloads cryptographic overhead from your applications. For self-hosters running multiple services behind a single public IP, a good TLS termination proxy is essential infrastructure. If you&amp;rsquo;re also evaluating &lt;a href="../haproxy-vs-envoy-vs-%5Bnginx%5D(https://nginx.org/)-load-balancer-guide/">load balancing options&lt;/a>, note that many load balancers double as TLS termination proxies — the line between the two roles is often blurred.&lt;/p></description></item><item><title>cert-manager vs LEGO vs acme.sh: Self-Hosted TLS Certificate Automation Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-19-cert-manager-vs-lego-vs-acme-sh-self-hosted-tls-certificate-automation-guide-2026/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-19-cert-manager-vs-lego-vs-acme-sh-self-hosted-tls-certificate-automation-guide-2026/</guid><description>&lt;p>Managing TLS certificates manually is one of the most common causes of service outages. Expired certificates bring down websites, break API endpoints, and disrupt email delivery. In 2026, the solution is straightforward: automate certificate provisioning and renewal using a self-hosted ACME client.&lt;/p></description></item><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>