• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Let's Encrypt & Domain without hosting

WhiteTiger

Basic Pleskian
I need to create a certificate for a domain with the "Let's Encrypt" extension.

Domain is mapped to a multisite WP through an alias.
So in Plesk I have to configure:
  • maindomain.com (with WP multisite)
  • *.maindomain.com
  • second-domain.com (no hosting)
  • second-domain.maindomain.com alias of second-domain.com
This is working properly (with http).
Now I want the user to use https as well.
  • https// maindomain.com
  • https// second-domain.com
Now with the "Let's Encrypt" extension I can create a certificate for maindomain.com, but in the list I do not find the domain second-domain.com, perhaps because it is declared "no hosting".

But, if I create second-domain.com associated with a folder, I do not think that the alias still works because it would point to this folder instead of second-domain.maindomain.com. Or not?

Thanks in advance for any advice.
 
Hi WhiteTiger,

pls. note, that the Let's Encrypt certificate validation procedure is to place a ( temporary ) file in a folder called ".well-known", which is impossible, if you decided to setup "no hosting" for your alias. ;)

You are certainly able to use the option string "--webroot-path" with your desired path, but you have to do this over the command line ( logged in as user "root" ), without using the Plesk Control Panel.

Example:
Code:
plesk bin extension --exec letsencrypt cli.php --domain maindomain.com --domain second-domain.com --webroot-path /var/www/vhosts/maindomain.com/httpdocs --email [email protected]
Pls. inspect your "panel.log" for possible issues, when you use this command and pls. post the depending entries in case that you need help with possible investigations. ;)


Additional informations:


Sometimes, it is as well a good idea to change the log - level ( TEMPORARILY! ), to get more informations in Plesk - log - files:

 
Thanks for the answer, but I do not understand one thing.
Where is the "well-known" folder located? I do not see it anywhere.

Waiting for an answer I have made some tests.

I created the "second-domain" domain as a "hosting" with an own folder because I knew that in this Plesk would create files.
Then I changed the domain configuration by pointing to the "maindomain" folder.
Finally I created the certificate.
Everything is working, having now the two domains reachable by https:

But I did not know what you said to me now, about the folder and the temporary file.
My fear is that the two files will be created at the same point and if they have the same name they will overlap each other.
However, as I said, I do not see this folder.
 
Hi WhiteTiger,

to check my above informations, pls. inspect your "panel.log", where the Plesk Let's Encrypt Extension will log it's actions. You will then see as well, that the ( temporary ) folder will be created AND deleted as well after the whole validation process. ;)

If you desire to leave the folder, you have to setup in your "panel.ini" ( => /usr/local/psa/admin/conf ) for example:
Code:
...
[ext-letsencrypt]

disable-cleanup = true
...
More informations can be found at the Plesk documentation:

 
Back
Top