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

Resolved (Cloud server with multiple domains) SSL Wildcard not works with subdomains ftp/mail/webmail

MicheleB

Regular Pleskian
Hello,
I'd like to activate a Rapid SSL Wildcard for a specific domain on my cloud server (more domains/hosting hosted on the server) to encrypt the domain's activity on ftp, mail and webmail but it works only on generic subdomains (ex. mysubdomain.mydomain.com).

Sum up, it works on:
mydomain.com
www.mydomain.com
mygenericsubdomain1.mydomain.com
mygenericsubdomain2.mydomain.com
...

Not works on (view every time the default SSL certificate on Plesk):
ftp.mydomain.com
mail.mydomain.com
webmail.mydomain.com

Is it a correct behaviour or I've a Plesk configuration's problem?
Plesk allow only a unique Wildcard SSL for ftp/mail/webmail subdomains (the Wildcard SSL used for the primary domain on the cloud server, the default Plesk SSL)?
If is it a Plesk 12.5 limitation, the new Onyx has this features?

Thanks!
 
Last edited:
Hi MicheleB,

Is it valid also for ftp.mydomain.com?
No, because your ProFTP - server uses the configuration from "/etc/proftpd.conf" ( as for example: )

Code:
...
    TLSRSACertificateFile /opt/psa/admin/conf/httpsd.pem
    TLSRSACertificateKeyFile /opt/psa/admin/conf/httpsd.pem
...

But the mentioned solution for your unique certificate order and structure ( as mentioned for "servercert.pem", "postfix_default.pem" and "ssl-cert-and-key.pem" ) is certainly the exactly same solution for your ( new ) "httpsd.pem" - file:

...
  1. The Private Key
  2. The primary certificate
  3. The intermediate certificate
  4. The root certificate
...
 
Hi,
do I need to restart only qmail/postfix and courier-imap services with this command?
/usr/local/psa/admin/sbin/mailmng --restart-service

For "/etc/proftpd.conf" is necessary only save the new configuration?

Thanks
 
Back
Top