Unauthorized error Help!

[wilfredinni]

I have read other posts, but i haven’t been able to solve it. Thank you!

My domain is:
pythoncheatsheet.org

I ran this command:
sudo certbot certonly --webroot -w /home/wilfredinni/pysheetBlog/app/static -d pythoncheatsheet.org

It produced this output:
- The following errors were reported by the server:

Domain: pythoncheatsheet.org
Type: unauthorized
Detail: Invalid response from
http://pythoncheatsheet.org/.well-known/acme-challenge/HhEu7wcHnlVRsk1x6_SMX-67Qcbx-R89x9-Y8JWLcPI:
"

<title"

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.

My web server is:
nginx

The operating system my web server runs on is (include version):
ubuntu 16.04

My hosting provider, if applicable, is:
digitalocean

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

[stevenzhu]

Hi,

It seems you are using an cms system, which redirect the query to an 404 page.
You might want to use webroot authrncator and Apache installer.

For webroot, specify an directory else than your website directory’s to avoid redirection caused by your Nginx config.

Thank you

[JuergenAuer]

Hello @wilfredinni

@wilfredinni

Detail: Invalid response from
http://pythoncheatsheet.org/.well-known/acme-challenge/HhEu7wcHnlVRsk1x6_SMX-67Qcbx-R89x9-Y8JWLcPI

the page is redirected from http to https. But this doesn't work because there is a self-signed certificate.

So you should temporarily disable the 301 - redirect from http to https.

Later, when you have installed a correct and valide Letsencrypt-Certificate, this may work.

[schoen]

@JuergenAuer

the page is redirected from http to https. But this doesn’t work because there is a self-signed certificate.

So you should temporarily disable the 301 - redirect from http to https.

This isn't a correct diagnosis of the problem in this case, because the Let's Encrypt CA specifically ignores certificate validation errors resulting from a 301 redirection from HTTP to HTTPS when verifying HTTP-01 challenges. As a result, the behavior of the challenge URL in an ordinary browser isn't exactly reflective of what the CA will decide.

[schoen]

@stevenzhu

For webroot, specify an directory else than your website directory’s to avoid redirection caused by your Nginx config.

But if the CMS is redirecting all queries, then there is no other directory that could be specified with -w. An exception in the CMS redirection would need to be added to allow the contents of /.well-known/acme-challenge to be served as static files.

[JuergenAuer]

@schoen

because the Let’s Encrypt CA specifically ignores certificate validation errors resulting from a 301 redirection from HTTP to HTTPS when verifying HTTP-01 challenges

Ah, thanks for your correction. Good to know.

[stevenzhu]

@schoen

But if the CMS is redirecting all queries, then there is no other directory that could be specified with -w . An exception in the CMS redirection would need to be added to allow the contents of /.well-known/acme-challenge to be served as static files.

However, since he is using nginx, cms would add redirection on Nginx vHost rather than htaccess (which is Apache ). If using webroot, it will avoid the vHost(if I remembered correctly)

Thank you

[wilfredinni]

Solved. Finally did a txt record and uploaded them manually