• 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.

Question Let's Encrypt: renewal of certificates with manually added add-on domains

ronv

Basic Pleskian
Hi,

I'm running a Linux server with the Plesk (Onyx, version 17) LetsEncrypt extension (version 2.5.1). I want to secure some aliases of a subdomain that are defined with the ServerAlias directive in an Apache configuration file. (Note: the reason for this setup is that the Plesk interface doesn't allow to define aliases for subdomains, only for main domains.)

I’ve successfully managed to add domain aliases to a certificate with the -d option on the command-line:

Code:
plesk bin extension --exec letsencrypt cli.php --expand -d sub.domain.com -d subalias1.domain.com -d subalias2.domain.com --webroot-path "/var/www/vhosts/domain.com/sites/sub.domain.com"

So far, so good, but I’m still waiting for the renewal date to see what will happen. I’m wondering: when the certificate will be automatically renewed, will all domain aliases be included again, or will only sub.domain.com be included in the new certificate?

Note: I've noticed this in the release notes for version 1.3 of the LE Plesk extension:
[+] Store CLI options for certificate renewal (issue #46)
...which seems to suggest that the automatic renewal process might remember to renew all add-on domains as well, but I'm not sure if I'm understanding correctly (the issue referred to is
Have console command for automated deployment. · Issue #46 · plesk/letsencrypt-plesk · GitHub)

Any clarification would be much appreciated!

Ron
 
Last edited:
Back
Top