• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

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.
 
Back
Top