/.well-known directory gets created, but error "Could not connect..."


#1

Using
./letsencrypt-auto certonly -a webroot --webroot-path=/usr/share/nginx/html -d www.mydomain.com
with NGINX.
Verified NGINX serves files from /usr/share/nginx/html, and I see the /.well-known getting created, but the error keeps popping up:
“Could not connect to http://www.mydomain.com/.well-known
/acme-challenge/toYKYPfgH7DIU1txeng1jdXAiGoBJkKPrR1Bnjzhh_U”


Could not connect to http://domain.name.org/.well-known/acme-challenge/xxxx
#2

If you create a “test” file in /usr/share/nginx/html/.well-known/acme-challenge/test

with contents “working ok” or similar.

Can you then reach it, from the internet via http://www.yourdomain.com/.well-known/acme-challenge/test and it just provide the plain text response “working OK” ?


#3

My mistake was not having access to the site via port 80.
Once I did that, it worked.
Problem solved.
Thanks very much for the response, and the excellent service.
I really like LetsEncrypt a lot.


#4

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