<?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 Support Tools</title><link>https://support.tools/tags/ssl/</link><description>Recent content in SSL on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 01 Jun 2025 12:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/ssl/index.xml" rel="self" type="application/rss+xml"/><item><title>Easier Alternative to Nginx + Let’s Encrypt with Caddy Docker Proxy</title><link>https://support.tools/caddy-docker-proxy/</link><pubDate>Sun, 01 Jun 2025 12:00:00 -0500</pubDate><guid>https://support.tools/caddy-docker-proxy/</guid><description>&lt;p&gt;Managing SSL certificates and proxying Docker applications has traditionally required a combination of Nginx and Let’s Encrypt. While effective, this setup can feel overly complex for many use cases. Enter &lt;strong&gt;Caddy Docker Proxy&lt;/strong&gt;, a tool that simplifies this process, making it ideal for small applications or CI/CD pipelines.&lt;/p&gt;</description></item><item><title>How to Get Chrome to Accept a Self-Signed Certificate</title><link>https://support.tools/post/chrome-accept-self-signed-certificate-guide/</link><pubDate>Fri, 13 Oct 2023 09:30:00 -0500</pubDate><guid>https://support.tools/post/chrome-accept-self-signed-certificate-guide/</guid><description>&lt;p&gt;This guide explains how to make Chrome accept a self-signed certificate. It is based on Chrome 68 on Windows 10, but the steps should be similar for other versions and platforms.&lt;/p&gt;&#10;&lt;h2 id="how-to-get-chrome-to-accept-a-self-signed-certificate"&gt;&lt;a href="#how-to-get-chrome-to-accept-a-self-signed-certificate"&gt;How to Get Chrome to Accept a Self-Signed Certificate&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;If you&amp;rsquo;re working with a self-signed certificate and need to make Chrome accept it, here&amp;rsquo;s a step-by-step procedure that works for Chrome 68 on Windows 10. This method allows you to trust the certificate and use it without encountering constant security warnings.&lt;/p&gt;</description></item><item><title>vSphere 7 – Certificates with VMCA as Subordinate</title><link>https://support.tools/post/vsphere-7-certificates-with-vmca-as-subordinate/</link><pubDate>Tue, 07 Sep 2021 07:46:00 +0000</pubDate><guid>https://support.tools/post/vsphere-7-certificates-with-vmca-as-subordinate/</guid><description>&lt;p&gt;For enterprises that need fully trusted SSL certificates for the vSphere 7.0 environment, you have two basic options:&lt;/p&gt;&#10;&lt;p&gt;Full Custom Mode: Manually replace all certificates for vCenter and the ESXi hosts with your trusted certificates.&#10;Subordinate CA Mode: Use the built-in VMCA service as an official subordinate CA of your existing PKI infrastructure. After the initial configuration, automates the issuing of SSL certs for your vSphere environment. This is the method covered in this blog post.&#10;VMware offers two other certificate options: Fully Managed and hybrid mode, for a total of four certificate options. You can find out more about all of them in this VMware blog post.&lt;/p&gt;&#10;&lt;p&gt;In a high-security environment, it is very likely the security team will NOT let you configure the vCenter VMCA as a subordinate CA. So, you will be left with the full custom mode if you want 100% of the certificates trusted. However, if you are in a situation where you can configure the VMCA as a subordinate CA, this post is for you!&lt;/p&gt;&#10;&lt;p&gt;Note: Before you do this replacement in production, I strongly urge you to set up a test vCenter instance and run this entire procedure. Botched certificate replacements can lead to bad days. And another tip for a lab test is to snapshot the vCenter VM before you try the process. That way, you can easily roll back should things go south.&lt;/p&gt;</description></item><item><title>How to change the Rancher v2.x Server certificate to an externally created certificate.</title><link>https://support.tools/post/how-to-change-rancher-2.x-server-cert/</link><pubDate>Mon, 01 Mar 2021 11:10:00 +0000</pubDate><guid>https://support.tools/post/how-to-change-rancher-2.x-server-cert/</guid><description>&lt;p&gt;It&amp;rsquo;s often necessary to migrate from a self-signed or LetsEncrypt certificate to an externally created certificate like DigiCert or Comodo in Rancher v2.x.&lt;/p&gt;</description></item></channel></rss>