Unable to secure a domain with a Let's Encrypt certificate:
PLESK_ERROR: Error: Could not issue a Lets Encrypt SSL\TLS certificate for test.occucare.co.in.
Authorization for the domain failed.
Additional error details:
Invalid response from https://acme-v01.api.letsencrypt.orgiacme/authz/PzGYc-Dg7.1YYmq8ni3v_-6 fU_ZWiliw6AzB5icsLOQ.
Details: Type: urn:acme:error:connection
Detail: Fetching https://example.com/well-known/acme-challenge/DVVVq7.1DOViciA35pjhtl3aA01jr2hFMeyul24a7WEUY:
Connection reset by peer
- At Domains > example.com > Hosting Settings one or both options are enabled:
Permanent SEO-safe 301 redirect from HTTP to HTTPS is checked.
Preferred domain is set either to example.com or to www.example.com.
- There is a 302 redirect to another domain:
# curl example.com
<p>The document has moved <a href="http://example2.com">here</a>.</p>
Redirect is enabled.
Issuing certificate is possible only after passing the challenge.
Challenge works only via HTTP and no redirection, e.g, to www.example.com, should be enabled.
In case of 302 redirect in Plesk, check Subscription > example.com > Hosting Settings:
It is not possible to issue a certificate for the domain which has forwarding configured.
To issue the certificate, turn off domain forwarding by changing Hosting type to Hosting in Domains > example.com > Hosting Settings.
- In case of 302 redirect to another server:
Cancel the custom modifications of the domain configuration.
In case of 301 redirect: Check if Domain forwarding is enabled for example.com:
In Plesk go to Domains > example.com > Hosting Settings and perform the following steps:
Set Preferred domain to none.
Uncheck the option Permanent SEO-safe 301 redirect from HTTP to HTTPS.
Issue a Let's Encrypt certificate in Domains > example.com > Let's Encrypt.