<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cockpit on TODO: Document</title>
    <link>https://ryan.lovelett.me/tags/cockpit/</link>
    <description>Recent content in Cockpit on TODO: Document</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Mar 2021 21:55:37 -0500</lastBuildDate><atom:link href="https://ryan.lovelett.me/tags/cockpit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Let&#39;s Encrypt certificates with Cockpit</title>
      <link>https://ryan.lovelett.me/posts/letsencrypt-cockpit/</link>
      <pubDate>Wed, 10 Mar 2021 21:55:37 -0500</pubDate>
      
      <guid>https://ryan.lovelett.me/posts/letsencrypt-cockpit/</guid>
      <description>After installing Cockpit you will likely end up with certificates that are self-signed and therefore untrusted by default.
There is a better way; Let&amp;rsquo;s Encrypt.
NOTE: Through out the article the fully-qualified domain name of the Cockpit server is treated as a variable (e.g., $FQDN). Make sure to either define a similar variable with an appropriate value or replace it when copying the commands.
Install certbot First thing is first, install certbot1.</description>
    </item>
    
  </channel>
</rss>
