<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lets-Encrypt on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/lets-encrypt/</link>
    <description>Recent content in Lets-Encrypt on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted HAProxy SSL/TLS Automation: haproxy-acme vs certbot-haproxy vs acme.sh Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-haproxy-acme-ssl-automation/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-haproxy-acme-ssl-automation/</guid>
      <description>&lt;p&gt;HAProxy is one of the most battle-tested reverse proxies and load balancers in the self-hosted world. But managing SSL/TLS certificates manually is a recipe for expired certs and midnight outages. The solution: automate certificate renewal directly with HAProxy. Three tools dominate this space — each with different integration approaches and trade-offs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
