---
title: "Comment by Node Edge Ops on \"How To Secure Nginx with Let's Encrypt on Ubuntu 20.04\" | Hashnode"
description: "On Ubuntu I keep Certbot renew on a timer and always run nginx -t before reload in the deploy-hook. HTTP-01 failures are usually a missing server_name or the ch"
url: "https://hashnode.com/posts/how-to-secure-nginx-with-lets-encrypt-on-ubuntu-2004/6981462181df426d1e826213/comment/6ae5207d9e7c87c38ce3c85a"
---

[Discussion](https://hashnode.com/posts/how-to-secure-nginx-with-lets-encrypt-on-ubuntu-2004/6981462181df426d1e826213)

Comment [How To Secure Nginx with Let's Encrypt on Ubuntu 20.04](https://hashnode.com/posts/how-to-secure-nginx-with-lets-encrypt-on-ubuntu-2004/6981462181df426d1e826213)

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

[Oct 30](https://hashnode.com/posts/how-to-secure-nginx-with-lets-encrypt-on-ubuntu-2004/6981462181df426d1e826213/comment/6ae5207d9e7c87c38ce3c85a)

On Ubuntu I keep Certbot renew on a timer and always run nginx -t before reload in the deploy-hook. HTTP-01 failures are usually a missing server\_name or the challenge path getting proxied away from nginx.
