• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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

D
Issue can only create webmail certificates
Replies
1
Views
759
deepnpisgah
D
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
10K
gsk
gsk
hansitheking
Resolved Let's Encrypt: Timeout during connect (likely firewall problem)
Replies
4
Views
9K
trialotto
T
AndyM
Question How to apply an SSL Let's Encrypt certificate to a custom port?
Replies
4
Views
4K
AndyM
AndyM
Azurel
Forwarded to devs Could not renew Let`s Encrypt certificates because of rateLimited
Replies
6
Views
3K
Azurel
Azurel
Back
Top