<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Devops on Nathanael&#39;s Blog</title>
    <link>https://blog.nathanaelbonfim.com/tags/devops/</link>
    <description>Recent content in Devops on Nathanael&#39;s Blog</description>
    <generator>Hugo -- 0.157.0</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Apr 2025 03:30:14 +0000</lastBuildDate>
    <atom:link href="https://blog.nathanaelbonfim.com/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debugging Nginx: why your SSL certificates don&#39;t apply after reload?</title>
      <link>https://blog.nathanaelbonfim.com/posts/debugging-nginx-why-your-ssl-certificates-dont-apply-after-reload/</link>
      <pubDate>Mon, 14 Apr 2025 03:30:14 +0000</pubDate>
      <guid>https://blog.nathanaelbonfim.com/posts/debugging-nginx-why-your-ssl-certificates-dont-apply-after-reload/</guid>
      <description>&lt;p&gt;Recently, an automation that creates new nginx hosts stopped working properly.
The process would go through flawlessly, but when I tried to access the site,
it redirected to another host. The same thing also occurred in certificate
renewals. Only after a full nginx restart would the site work correctly.&lt;/p&gt;
&lt;p&gt;This behavior led me down a debugging rabbit hole. In this post, I&amp;rsquo;ll share how
I diagnosed this issue and the solution I found to fix it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
