• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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