<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SSL on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/ssl/</link>
    <description>Recent content in SSL on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 03 Jul 2024 15:32:41 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/ssl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use LXC containers to build V2Ray and Caddy services on Alpine Linux to provide IPv6-based SSL WebSocket proxy</title>
      <link>https://blog.margrop.net/en/post/setting-up-v2ray-and-caddy-on-alpine-linux-lxc-container/</link>
      <pubDate>Wed, 03 Jul 2024 15:32:41 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/setting-up-v2ray-and-caddy-on-alpine-linux-lxc-container/</guid>
      <description>Preface In the modern Internet environment, proxy services are becoming more and more important, especially when it is necessary to break through geographical restrictions and improve privacy protection. This article will introduce in detail how to use V2Ray and Caddy to build an SSL WebSocket proxy service provided through IPv6 and domain name on the LXC container of the Alpine Linux 3.19 operating system.&#xA;Environment preparation Make sure your LXC container is running and has an IPv6 address assigned.</description>
    </item>
    <item>
      <title>Let&#39;s Encrypt automatically synchronizes Proxmox VE and DSM certificates after automatic renewal</title>
      <link>https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/</link>
      <pubDate>Tue, 02 Feb 2021 19:19:38 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/</guid>
      <description>Last time we talked about Let&amp;rsquo;s Encrypt通过DNS TXT记录来验证域名有效性, and the last part of the article was about how to use certbot renew for automatic renewal. Then the automatic renewal is successful, how to synchronize it to PVE and DSM?&#xA;Below we use a script to perform automatic synchronization.&#xA;Need to configure SSH password-free login on Proxmox VE and DSM servers Automatically synchronize Proxmox VE certificate Proxmox VE synchronized to this machine Proxmox VE synchronized to LAN cp /etc/letsencrypt/live/blog.</description>
    </item>
    <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>
