<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Lets-Encrypt - Tag - vo.rs</title><link>https://vo.rs/tags/lets-encrypt/</link><description>Lets-Encrypt - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Wed, 09 Oct 2024 08:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/lets-encrypt/" rel="self" type="application/rss+xml"/><item><title>Let's Encrypt Rate Limits: What to Do When You Hit the Wall</title><link>https://vo.rs/story/lets-encrypt-rate-limits-what-to-do-when-you-hit-the-wall/</link><description>&lt;p&gt;Let&amp;rsquo;s Encrypt is one of the genuinely great things to happen to the open web. Free, automated, universally trusted TLS certificates — the whole reason your homelab services have padlocks now instead of a wall of browser warnings. It is also a free service handling staggering volume, and it protects itself with rate limits. The trouble is you only ever learn those limits exist at the precise moment you slam into one, usually at 2am, usually while debugging something else, usually with a renewal cron job hammering away making everything worse.&lt;/p&gt;</description><pubDate>Wed, 09 Oct 2024 08:00:00 +0000</pubDate></item></channel></rss>