Failed authorization procedure

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: ptdevs.net

I ran this command: sudo certbot certonly --nginx

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?

1: ptdevs.net
2: www.ptdevs.net

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 1
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ptdevs.net
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. ptdevs.net (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://ptdevs.net/.well-known/acme-challenge/dSNEb1cUR8IryAKRi-WFXFzqsrKEpZMSumE0TSqKxMk [2a01:7e01::f03c:92ff:feeb:d152]: “\r\n404 Not Found\r\n<body bgcolor=“white”>\r\n

404 Not Found

\r\n
”

IMPORTANT NOTES:

My web server is (include version): nginx version: nginx/1.14.0 (Ubuntu), Django backend

The operating system my web server runs on is (include version): Ubuntu 18.04LTS

My hosting provider, if applicable, is: Linode

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0

2

Your nginx configuration is incomplete for your IPv6 address.

You will want to open up your nginx configuration, find the listen directive, and make sure the virtualhost is bound to both IPv4 and IPv6 like:

listen 80;
listen [::]:80;

then reload nginx.

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.