<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Certbot on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/certbot/</link>
    <description>Recent content in Certbot on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 19 Jan 2021 10:39:58 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/certbot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Let&#39;s Encrypt verifies domain name validity through DNS TXT records</title>
      <link>https://blog.margrop.net/en/post/lets-encrypt-use-dns-txt-acme-challenge-domain-available/</link>
      <pubDate>Tue, 19 Jan 2021 10:39:58 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/lets-encrypt-use-dns-txt-acme-challenge-domain-available/</guid>
      <description>When we use letsencrypt to obtain the free HTTPS certificate, letsencrypt needs to verify the domain name. By default it authenticates like this:&#xA;The certbot program places a file in the root directory of the web directory. The server of letsencrypt accesses this file through the domain name to verify that the domain name you applied for belongs to you. But sometimes we want to set HTTPS for a certain host on the intranet.</description>
    </item>
  </channel>
</rss>
