letsencrypt=2 with nginx standalone server.

zEitEr

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
15,188
Location
GMT +7.00
Hello,


It turns out that Directadmin creates .well-known/ (to verify a domain) under the domain's public_html with 711 permissions which are not sufficient, and

Code: 
chmod 755 .well-known/

solves the issue. With 711 we access an 403 error in NGINX:

Code: 
aaa.bbb.ccc.ddd - - [14/Dec/2016:06:19:34 +0100] "GET /.well-known/acme-challenge/letsencrypt_1481692773 HTTP/1.1" 403 162 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"

Let's encrypt client 1.0.3 is installed.

Kindly check this and fix it's required.
 
same happens when using letsencrypt=1
I just switched from Apache to Nginx and encountered the same problem for creating and updating certificates. I had to chmod both directories (.well-known and .well-know/acme-challenge) before getting a 200 http response on the test (as described on https://help.directadmin.com/item.php?id=646). After chmodding both and performing the test, the certificate was successfully created.
 
You must log in or register to reply here.
Back
Top