E H
My feedback
1 result found
-
298 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
An error occurred while saving the comment An error occurred while saving the comment E H commentedSo, another try since my first comment is not available anymore...
The following workaround works for me and I can secure the subdomain from mailman 'lists.my-domain.com' with my Lets-Encrypt certificate from my main domain.
This workaound might only work in single domain setups.1. Secure your domain with a Let's Encrypt certificate (or any other of your choice, should also work). Make sure, it is a wildcard certificate (securing *.my-domain.com)
2. Open the details of your certificate. In my German plesk variant it is under 'Websites and Domains' - 'SSL and TSL certificates' - 'Erweiterte Einstellungen' (Advanced Settings maybe?) - click on your certificate - You'll see the page with your private key, the crt and the ca-crt
3. Open a new tab and goto 'Tools and Settings' - 'SSL and TSL certificates' - click on '+ Add' and paste the private key, the crt and ca-crt in the corresponding inputs
4. make the newly added cert the defaultThat is it.
The caveat is that you have to repeat this process whenever your domain certificate expires...
An error occurred while saving the comment E H commentedHello Plesk Staff Admins! What happened to my comment? I posted a workaround for this issue...
Why did it disappear?E H supported this idea ·
If somebody is able to write a terminal script to automate the process mentioned in my previous comment, that would be awesome! We could run it as a cron job and would have a self-made implementation. If the plesk-team does not provide us with a solution we could make it ourselves.