<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Certificates on Thoughts and Ramblings by Mike</title><link>https://mikedent.io/tags/certificates/</link><description>Recent content in Certificates on Thoughts and Ramblings by Mike</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Mike Dent</copyright><lastBuildDate>Sun, 03 May 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://mikedent.io/tags/certificates/index.xml" rel="self" type="application/rss+xml"/><item><title>Updating SSL Certificates for CML</title><link>https://mikedent.io/post/2026/5/updating-ssl-certificates-for-cml/</link><pubDate>Sun, 03 May 2026 09:00:00 -0400</pubDate><guid>https://mikedent.io/post/2026/5/updating-ssl-certificates-for-cml/</guid><description>
&lt;p&gt;If you have a Cisco Modeling Labs appliance in your lab or running on a piece of dedicated hardware, you have probably noticed two browser warnings every time you log in. CML ships with self-signed certs on both the main web UI and the Cockpit management UI, and your browser will complain about both. Cisco publishes an &lt;a href="https://developer.cisco.com/docs/modeling-labs/installing-ssl-certificate/"&gt;official guide for installing an SSL certificate on CML&lt;/a&gt;, and it is a solid starting point, but in my own runs it did not get me 100% of the way to the outcome I wanted. The procedure focuses on the nginx side, leaves Cockpit's quirks largely unaddressed, and does not cover renewal, rollback, or any pre and post checks. The helper script in this post fills those gaps so a single command handles the install, the renewal six months from now, and a rollback if something goes sideways. This post walks through what the script does, how to use it, and how to keep things tidy when your wildcard cert renews.&lt;/p&gt;</description></item></channel></rss>