I'm trying to setup Let's Encrypt certbot on a docker container hosted on nginx. Since nginx is just a proxy-pass to a docker container, I'm forwarding requests to .well-known to the disk location /.well-known/acme-challenge/ { root /var/www/certbot; } and calling it like this ce…

[image] Mystery: Not seeing anything wrong. What else am I missing? You are missing a listen statement for IPv6. You need one for each (v4 and v6) like: [image] Mystery: listen 80; listen [::]:80; Without that nginx will not select that server block for IPv6 incoming requ…

[image] Mystery: certbot --nginx --webroot-path /var/www/certbot -d dev.satrimono.com Hi @Mystery , The trouble is that the --webroot-path option is ignored by the --nginx plugin. (Maybe it should give a more explicit error!) The --nginx method (when used as an authenticator, that is, to pr…

What happens with your watch command? (If you want to get fancier, you could also use inotifywait!) If you'd like to check your setup at the moment that Certbot believes it's satisfied the challenge (so for example with the file actually existing), you can add the --debug-challenges option; then yo…

The file DOES get created. I can access the file from my browser. http://dev.satrimono.com/.well-known/acme-challenge/PqIvQBg_1B14y5trRCvroFKYI3NlFn0OJHfZRaNwt3c So then why does it fail when I press Enter?

Can you share more of the error output that Certbot displays from the certificate authority?

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported theseproblems: Domain: dev.satrimono.com Type: unauthorized Detail: 2001:19f0:5401:34d:5400:4ff:fee3:fe9: Invalid response from http://dev.satrimono.com/.well-known/acme-challenge/LmQ812-Q3vRaJ…

Thanks. Your IPv4 and IPv6 servers are returning different content. Presumably the IPv4 version is working as expected and the IPv6 version isn't. Can you check into how to harmonize their behaviors?

I was just thinking of that; saw that Facebook Debugger was returning the Default website (welcome to nginx) instead of the website. "dev" DNA records point to the server for both IPv4 and IPv6. "2001:19f0" is indeed the right server. nginx default website is untouched. This is the website config…

[image] Mystery: certbot --nginx --webroot-path /var/www/certbot -d dev.satrimono.com To clarify this entanglement a bit further... Not only does the --nginx override/conflict with --webroot. But the webroot plugin parameter used itself is incomplete; As it requires two parts: --webroot …

Certbot not creating .wellknown/acme-challenge file

Help

MikeMcQ May 2, 2024, 1:03pm 10

You are missing a listen statement for IPv6. You need one for each (v4 and v6) like:

Without that nginx will not select that server block for IPv6 incoming requests

New SSL generation on Ngnix fails when domain has AAAA record

Topic		Replies	Views
Certbot certonly webroot fail to create challenge file Help	4	2968	September 27, 2018
Certbot failing to create .well-known files Help	24	7271	January 17, 2021
Certbot not generating file Help	2	2914	October 15, 2018
[nginx, docker] certbot certifcates - challenge webroot Help	2	861	November 30, 2022
Failure Creating Certificate - acme-challenge - 404 error - nginx - AWS Help	6	4755	May 12, 2020

Certbot not creating .wellknown/acme-challenge file

Related topics