<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Letsencrypt on qvarnstr0ms blog thing</title><link>https://qvarnstr0m-blog.spwnr.io/tags/letsencrypt/</link><description>Recent content in Letsencrypt on qvarnstr0ms blog thing</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://qvarnstr0m-blog.spwnr.io/tags/letsencrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Cert issue</title><link>https://qvarnstr0m-blog.spwnr.io/posts/2026-05-09-cert-issue/</link><pubDate>Sat, 09 May 2026 10:00:00 +0200</pubDate><guid>https://qvarnstr0m-blog.spwnr.io/posts/2026-05-09-cert-issue/</guid><description>&lt;p&gt;So the other day I noticed that spwnr.io was showing one of those lovely browser warnings. You know the one. &amp;ldquo;Your connection is not private.&amp;rdquo; The kind of message that makes you look like you&amp;rsquo;re running a phishing operation. Not a great look.&lt;/p&gt;
&lt;p&gt;My first thought was that the Let&amp;rsquo;s Encrypt certificate had expired. Which would be embarrassing, but fair, these things happen when you&amp;rsquo;re a one-person operation and don&amp;rsquo;t check in on your servers every day. So I SSH&amp;rsquo;d in and ran &lt;code&gt;certbot certificates&lt;/code&gt;, fully expecting to see an expired cert staring back at me.&lt;/p&gt;</description></item></channel></rss>