created May 14, 2020
I have been using SSL/TLS at https://soupmode.com, since the fall of 2013. Soupmode is my private, web-based messaging app that I have used with family. It's rarely used now.
I host soupmode.com on a Digital Ocean Droplet. I host many soupmode.com subdomain test websites and several top level domain name websites, such as sawv.org on the same Droplet.
Initially, I used another TLS cert provider. A few years ago, I switched to Let's Encrypt. I needed to renew the cert for soupmode.com soon. Today, I renewed the cert, and I added sawv.org.
I host static HTML pages at sawv.org, but I create and update those static HTML pages by using my small, web-based static site generator. I type mainly in Markdown.
After including sawv.org in the TLS cert, I had to modify the YAML config file that I use with my simple CMS to change the API URL to point to https. No biggie. I may encounter other issues.
sawv.org is slightly slower with the TLS cert, according to webpagetest.org. First view, fully loaded times for a basic web page have increased from approximately .250 seconds to .400 seconds. I suppose that I will survive this change.
The main reason for including sawv.org in the TLS cert today was to support Gemini, which requires TLS. I planned to make sawv.org use TLS eventually. The switch was painless. I did not need to make any changes to the Nginx config file for sawv.org. It simply worked. Nice. I should have done this sooner.
A year or two ago, I switched http://toledoweather.info to use TLS, but afterward, some image embeds stopped working because the images were hosted on other servers that used http. But over the past couple years, the NWS has switched its severs to use https. I think that I could now switch toledoweather.info to use TLS without issues.