• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Let's Encrypt nameserver certificate creation failure

PDXMember

New Pleskian
I am getting the following error when trying to secure Plesk Onyx 17.5.3 Update #6:

Code:
Error: Execution letsencrypt-hostname.sh has failed with exit code 1, stdout: , stderr: [2017-05-28 21:55:23] ERR [extension/letsencrypt] Execution of /usr/local/psa/admin/plib/modules/letsencrypt/scripts/cli.php failed with exit code 1 and the output:
Challenge marked as invalid. Details: Could not connect to ns1.mydomain.com
Execution of /usr/local/psa/admin/plib/modules/letsencrypt/scripts/cli.php failed with exit code 1 and the output:
Challenge marked as invalid. Details: Could not connect to ns1.mydomain.com

exit status 1

I can directly access the ns1.mydomain.com address from the address bar, I hvae also confirmed it with whatismydns.com checking it to ensure it is facing the proper IP. Nothing in that area has changed for my domain record since Dec. 2016.

My main site that I run, I was able to install LetsEncrypt SSL certificate without issues before this.

I am running on a VPS with CentOS Linux release 7.3.1611 (Core)
 
I guess I should point out - the main site that I am hosting is my blog which is running Wordpress. :)
The ns1.mydomain.com is the main URL for the Plesk installation.
 
When you
# curl ns1.mydomain.com
on the server you are trying to install the certificate on, does that return the content of your host default page?
 
No, but I think this might be the issue.

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

Digging now for where to change this in Plesk.

I think it is redirecting , but not sure where. My main site (Different domain name) forces visitors to use https, but I doubt this would be the cause?
 
That is definitely the issue, because in that case Let's Encrypt cannot create the files needed to authorize the certificate. Certificates cannot be created on redirected URLs.
 
Back
Top