diff --git a/posts/fullstack-hono.md b/posts/fullstack-hono.md
index 9b2fcf7..d329c81 100644
--- a/posts/fullstack-hono.md
+++ b/posts/fullstack-hono.md
@@ -188,13 +188,13 @@ Okay - sorry for the tangent, let me get back to the deployment of Dokku. If you
 The first thing we need to do - after setting up Dokku - is to create the Blog application.
 
 ```shell
-$ dokku apps:create davesmithhayes.com
+dokku apps:create davesmithhayes.com
 ```
 
 After that, I would need to set the new remote in my Git repository:
 
 ```shell
-$ git remote add dokku dokku@davesmithhayes.com:davesmithhayes.com
+git remote add dokku dokku@davesmithhayes.com:davesmithhayes.com
 ```
 
 And simply do a:
@@ -202,3 +202,23 @@ And simply do a:
 ```shell
 git push -u dokku main
 ```
+
+Or so I thought. Once the application was deployed and declared running, I went to [https://davesmithhayes.com](https://davesmithhayes.com) and noticed right away I had no SSL. Looking at my Bash history I noticed I forgot to set up Let's Encrypt to get me an SSL for my website. So I did that through Dokku:
+
+```shell
+dokku letsencrypt:enable davesmithhayes.com 
+```
+
+Which failed. With this message:
+
+```
+Certificate retrieval failed!
+```
+
+I think this is failing because I have existing `certbot` set up for my old 11ty blog on this same host. So I revoked the certificae with `certbot`:
+
+```shell
+sudo certbot revoke --cert-name davesmithhayes.com
+```
+
+At this time Let's Encrypt had rate-limited my many, many failed attempts to get a new certificate for my own domain. Time to wait it out.