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

SSL in Domain Alias , How ?

Frank.P

Regular Pleskian
A Domain with IP dedicated work with SSL Certificate (HTTPS) , but the domain alias load the domain certificate and said wrong certificate because the domain is not the same.

MainDomain.com with SSL
DomainAlias.com with MainDomain.com SSL

How can I set for MainDomain.com the right SSL and for DomainAlias a domain alias certificate ?

Thanks
 
You can't do it in Plesk context.
As possible workaround you can create site DomainAlias.com with own certificate and then set up redirection to MainDomain.com site.
 
If you want same certificate covering both Domain and DomainAlias, you will need to buy so called multidomain certificate.
It is not about how Plesk works, but it is nature of SSL certificate - normally it includes exact domain name to validate.

IgorG's way (redirect) works as well.

Probable 3rd way would be configure DomainAlias.com as non-SSL domain with redirect to SSL Domain.com.
 
I need a domain alias and not redirect , because the customer never know the real domain and eahc domain need to get the same files.

I cannot get a certificate with multidomain , only 1 certificate for each domain.

I think this is important to upgrade for future plesk version. I suggest that.
 
You can only do this if you would use Cloudflare.
Setup the main--domain there.
and remove your certificate in Plesk
The non-SSL domain should be a real alias (without 301 redirect)
 
Use a SAN certificate on the main domain for this.


Let's Encrypt supports this by default:

https://community.letsencrypt.org/t/frequently-asked-questions-faq/26

"Can I get a certificate for multiple domain names (SAN certificates)?

Yes, the same certificate can apply to several different names using the Subject Alternative Name (SAN) mechanism. The resulting certificates will be accepted by browsers for any of the domain names listed in them."
 
Yes, SAN certificate could be the solution, but how they can be managed in plesk?

LE certificates are intended to be used with automated scripts and Plesk has a great extension to have this done.
But it does not support aliased domains, when aliasing a domain which uses Let's Encrypt, it generates a the scaring browser warning.
I suggest to add this feature 'cause the result resembles a problem and not a missing feature.

There is a feature request on User Voice, please subscribe it:
https://plesk.uservoice.com/forums/...ons/15013254-let-s-encrypt-add-domain-aliases

IgorG, don't you think this is urgent 'cause it seems an error on Plesk user side?

Thanks

Oto Tortorella
 
Last edited:
Just to point out that a workaround is to add a new domain and chose the Hosting type as Forwarding.
But the subscription should be able to add another domain and not an alias.

Regards
 
Back
Top