• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Vote Let's Encrypt support

WOuld you like to have free X509 certificate with Let's Encrypt initiative implemented with Plesk 12

  • Total voters
    56
Hi camaran,

IF the manual nginx shutdown didn't work for you, pls. make sure, that for example "watchdog" isn't restarting nginx automatically in the background. You can always check the status of a service with the command "service servicename status", so pls. check first, if the nginx webserver is really stopped during the creation procedure.

You should consider to post log - files from Let's encrypt, in case of any issues/problems/failures, which are located at "/opt/psa/var/modules/letsencrypt/logs". In addition, it would help as well to see log - files from apache and/or nginx for investigations ( pls. note that domain - specific webserver logs are located at: "/var/www/vhosts/system/YOUR-DOMAIN.COM/logs" ).
 
Hi camaran,

my fault... I didn't have a closer look at your first stated error message:

Code: 
Domain: adv.chatme.im
Type:   unauthorized
Detail: Invalid response from http://adv.chatme.im/.well-known/acme-challenge/uTl_3ENhNAUMBltNAwhc47My02j2GgKpwsEKAADu_bk: "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>

As you can see, the file "uTl_3ENhNAUMBltNAwhc47My02j2GgKpwsEKAADu_bk" was not being served; instead the client received the "403" error - page. There are two possible causes:

Either the hosting provider is blocking the request for the IP or domain "https://acme-v01.api.letsencrypt.org" ( 23.56.116.37 ), or for example "mod_security" is your root cause. Pls. check your log - files and ask as well your hosting provider, if they block some domain by default.
 
You must log in or register to reply here.

Similar threads

Hangover2
Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved
2 3
Replies
48
Views
22K
gsk
gsk
Azurel
Wrong expire certificate(s) mail
Replies
1
Views
1K
Bitpalast
Bitpalast
futureweb
Issue Let's Encrypt - CAA Rechecking Bug - Revoking certificates on March 4
Replies
5
Views
2K
futureweb
futureweb
learning_curve
Input Plesk / Let's Encrypt > Support for ECDSA Certificates
Replies
3
Views
2K
learning_curve
learning_curve
learning_curve
Question Let's Encrypt *Wildcard Certificates
Replies
13
Views
6K
learning_curve
learning_curve
Back
Top