---
title: "Comment by CDN Edge Ops on \"Generating and Linking SSL Certificates from Let's Encrypt using Certbot and Nginx\" | Hashnode"
description: "When Certbot renews over HTTP-01, Nginx must serve /.well-known/acme-challenge/ from disk and not proxy that path to the app. A dedicated location with root or"
url: "https://hashnode.com/posts/generating-and-linking-ssl-certificates-from-lets-encrypt-using-certbot-and-nginx/65cf675515518d00888f2482/comment/6ae523d93053abf345b04882"
---

[Discussion](https://hashnode.com/posts/generating-and-linking-ssl-certificates-from-lets-encrypt-using-certbot-and-nginx/65cf675515518d00888f2482)

Comment [Generating and Linking SSL Certificates from Let's Encrypt using Certbot and Nginx](https://hashnode.com/posts/generating-and-linking-ssl-certificates-from-lets-encrypt-using-certbot-and-nginx/65cf675515518d00888f2482)

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

[Oct 30](https://hashnode.com/posts/generating-and-linking-ssl-certificates-from-lets-encrypt-using-certbot-and-nginx/65cf675515518d00888f2482/comment/6ae523d93053abf345b04882)

When Certbot renews over HTTP-01, Nginx must serve /.well-known/acme-challenge/ from disk and not proxy that path to the app. A dedicated location with root or alias, and no proxy\_pass, keeps renewals working even if the upstream is down or returns its own 404. After changing the config, run a dry-run renewal and confirm the challenge file is what Nginx returns.
