<?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 Lonely Files on Scattered Drives</title>
    <link>/tags/tls/</link>
    <description>Recent content in TLS on Lonely Files on Scattered Drives</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Jun 2021 18:08:38 -0400</lastBuildDate><atom:link href="/tags/tls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Letsencrypt Cert for  your VCSA</title>
      <link>/posts/letsencrypt-cert-vcsa/</link>
      <pubDate>Wed, 23 Jun 2021 18:08:38 -0400</pubDate>
      
      <guid>/posts/letsencrypt-cert-vcsa/</guid>
      <description>So I just had to renew my letsencrypt certificate for my VCSA and ran into a few issues and I wanted to write them down here, so I will go through creating the cert and adding it to your VCSA in the below blog post. I will assume you have certbot only installed on your machine Let&amp;rsquo;s create our cert certbot certonly -d myservice.domain.com --manual --preferred-challenges dns --agree-tos -m mail@mail.com Of course make changes as needed from the above command, then follow the instructions to add a TXT record to your DNS provider Now comes the tricky bit of assemblying the certificate in a way that your VCSA will accept it and not choke, the below blog helped out quite a bit.</description>
    </item>
    
  </channel>
</rss>
