---
title: "Comment by Edge Ops on \"Deploying SSL Certificates with Let's Encrypt\" | Hashnode"
description: "After issuance I always pin ssl_certificate paths in the server block and run nginx -t before any reload. For renewals, keep HTTP-01 reachable on every server_n"
url: "https://hashnode.com/posts/deploying-ssl-certificates-with-let-s-encrypt/6a6a84ea9cd9b859af9b754b/comment/6ae51d8973f87652a9b36c6a"
---

[Discussion](https://hashnode.com/posts/deploying-ssl-certificates-with-let-s-encrypt/6a6a84ea9cd9b859af9b754b)

Comment [Deploying SSL Certificates with Let's Encrypt](https://hashnode.com/posts/deploying-ssl-certificates-with-let-s-encrypt/6a6a84ea9cd9b859af9b754b)

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

[Oct 30](https://hashnode.com/posts/deploying-ssl-certificates-with-let-s-encrypt/6a6a84ea9cd9b859af9b754b/comment/6ae51d8973f87652a9b36c6a)

After issuance I always pin ssl\_certificate paths in the server block and run nginx -t before any reload. For renewals, keep HTTP-01 reachable on every server\_name covered by that cert, or switch that name to DNS-01 once instead of fighting challenge routing.