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

Question Lets's Encrypt certificate domain alias

Twan Kouwenberg

New Pleskian
Hi ther I am new on the forum. And i just know the basics on Plesk.


We are running Appache an plesk 12.5.30 Update #35

The thing is as follows:

We do have a primary domain: example.co.uk and a domain alias example.de (in future will be many more)

Our primary domain is running on a single wordpress installation with wpml. On the primary domain we have installed the let's encrypt certificate. For what i now understand it is still not possible to install a letsencrypt certificate through Plesk on a domain alias.

What I want to know:
Is there a way to get the certificate also on the alias as it's is causing at this moment a warning of a unsecure site. Are there nice workarounds? Or cheap other alternatives for certificates who are also can be used on domain aliases?

BR Twan
 
Hi,

Did you ever get an answer for this as I am facing the same problem. I have a Magento installation that allows multi-site under the same CMS but would like to have a domain certificate each for .co.uk, .de etc?

Regards
Paul
 
You can define a subdomain, add a Let's Encrypt certificate, and then relocate every access to your main site. Using the 301 code it's even search engine-friendly.

Edit: I forgot to tell you the .htaccess code for the redirect:
RedirectMatch 301 ^(.*)$ http://www.xyz.com
 
You can define a subdomain, add a Let's Encrypt certificate, and then relocate every access to your main site. Using the 301 code it's even search engine-friendly.

Edit: I forgot to tell you the .htaccess code for the redirect:
RedirectMatch 301 ^(.*)$ http://www.xyz.com
If I'm not mistaken, certificate verification takes place before redirection?
 
Back
Top