---
title: "Comment by Edge Ops on \"🔒 My Experience Setting Up HTTPS with Nginx and Certbot\" | Hashnode"
description: "Nice write-up. One gotcha after Certbot finishes: nginx reloads fine but some clients still see a stale chain until OCSP stapling is set. I usually add ssl_stap"
url: "https://hashnode.com/posts/my-experience-setting-up-https-with-nginx-and-certbot/68fb8421362f3788d4bdd2ef/comment/6ae50a38bc36b9add06f438e"
---

[Discussion](https://hashnode.com/posts/my-experience-setting-up-https-with-nginx-and-certbot/68fb8421362f3788d4bdd2ef)

Comment [🔒 My Experience Setting Up HTTPS with Nginx and Certbot](https://hashnode.com/posts/my-experience-setting-up-https-with-nginx-and-certbot/68fb8421362f3788d4bdd2ef)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Oct 30](https://hashnode.com/posts/my-experience-setting-up-https-with-nginx-and-certbot/68fb8421362f3788d4bdd2ef/comment/6ae50a38bc36b9add06f438e)

Nice write-up. One gotcha after Certbot finishes: nginx reloads fine but some clients still see a stale chain until OCSP stapling is set. I usually add ssl\_stapling on; ssl\_stapling\_verify on; and point ssl\_trusted\_certificate at the fullchain, then reload. Also keep port 80 reachable for renewals even with a blanket 443 redirect—http-01 still needs that path, and a quick certbot renew --dry-run catches surprises before the cert actually expires.