<?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 Andrew Chilton</title>
    <link>https://chilts.org/tags/letsencrypt/</link>
    <description>Recent content in Letsencrypt on Andrew Chilton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-nz</language>
    <managingEditor>andychilton@gmail.com (Andrew Chilton)</managingEditor>
    <webMaster>andychilton@gmail.com (Andrew Chilton)</webMaster>
    <lastBuildDate>Thu, 14 Mar 2019 07:48:00 +0000</lastBuildDate>
    
	<atom:link href="https://chilts.org/tags/letsencrypt/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Let&#39;s Encrypt Notice, ACME TLS-SNI-01 Deprecation, Certbot Upgrade</title>
      <link>https://chilts.org/lets-encrypt-notice-acme-tls-sni-01-deprecation-certbot-upgrade/</link>
      <pubDate>Thu, 14 Mar 2019 07:48:00 +0000</pubDate>
      <author>andychilton@gmail.com (Andrew Chilton)</author>
      <guid>https://chilts.org/lets-encrypt-notice-acme-tls-sni-01-deprecation-certbot-upgrade/</guid>
      <description>Today I received an email from Let&amp;rsquo;s Encrypt regarding one of my domains. The cert was renewed recently with a deprecated validation method and therefore needs updating.
I&amp;rsquo;ve received one email like this before for a different domain on a different server, but couldn&amp;rsquo;t find my notes, so decided to publish them here so they can be found by other people.
Hello, Action may be required to prevent your Let&#39;s Encrypt certificate renewals from breaking.</description>
    </item>
    
  </channel>
</rss>