<?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 Marc JESTIN's Blog</title><link>https://blog.marcjestin.fr/en/tags/tls/</link><description>Recent content in Tls on Marc JESTIN's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.marcjestin.fr/en/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>Let's Encrypt caught in the Friday night maintenance syndrome</title><link>https://blog.marcjestin.fr/en/posts/lets-encrypt-caught-in-the-friday-night-maintenance-syndrome/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://blog.marcjestin.fr/en/posts/lets-encrypt-caught-in-the-friday-night-maintenance-syndrome/</guid><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;While I was getting ready to deploy a new service to visualize my traffic statistics, I briefly thought I had broken my &lt;code&gt;NPM&lt;/code&gt; (&lt;code&gt;Nginx Proxy Manager&lt;/code&gt;) configuration. Indeed, I was getting some rather vague errors and, when checking the &lt;em&gt;ad hoc&lt;/em&gt; folder, I couldn&amp;rsquo;t see any new directory for the key and certificate I was trying to obtain.&lt;/p&gt;
&lt;p&gt;It was only after checking the &lt;code&gt;Docker&lt;/code&gt; container logs that I realized the problem wasn&amp;rsquo;t on my end.&lt;/p&gt;</description></item></channel></rss>