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

RyanCA

New Pleskian
I'm very lost trying to set up a new SSL certificate for an existing domain; none of the guides I've tried seem to work. The domain is currently in a shared webspace on a shared IP.

What's the difference between adding an SSL certificate in the Server tab vs. the SSL certificates section under the domain? If I'm supposed to use the Server tab, why can't I see the certificate when I go into the domain?

How do I assign a dedicated IP to the domain? Plesk won't let me create a new webspace because the domain exists, but I don't think I can use multiple IP addresses for domains in a single webspace.

Thanks for any help!
 
Assuming you have already added the exclusive IP to Plesk itself (Tools&Settings >> IP addresses), you can change which IP is used for a domain by going to Subscriptions >> domain name then click on Change Hosting Settings. You'll be able to pick which IP the domain (or more accurately the Primary domain assigned to a Subscription) uses.

The main difference between adding an SSL in Tools & Settings >> SSL Certificates verses doing so in the Domain is that the Tools & Settings one is typically where you add certificates that you use to protect the panel itself, while the domain one is where you add one for an individual domain (or subscription, really).

If you have accidentally added your SSL for a domain via the Servers option, don't worry. You can just copy and paste the Certificate, Private Key and Intermediary certificate to the appropriate boxes in a newly added SSL certificate for the domain itself.

There is a little twist to things in that you can assign a certificate added via Tools & Settings >> SSL Certificates to be the default for a given IP address (click on the IP address in Tools & Settings >> IP Addresses). If this IP is Exclusive for a domain then that domain is typically then covered by that certificate. But it is not the right way to do it and can lead to unpredictable results.
 
Thanks Faris, the context helps a lot! Unfortunately, I'm still a bit stuck. This absolutely works when I change to the Service Provider view and go into the subscription. The problem is that the subscription has 7 domains in it, and I only want to put one of them on a different IP with an SSL certificate. The approach described above appears to only be viable if I want to change everything in the subscription. I don't see a way to move the domain to a new subscription or assign an IP to a single domain within a subscription (/webspace).

Any suggestions on how I approach this scenario?

Thanks again
 
It isn't too bad - you can achieve that you want, I hope:

The key is that although you can only have one SSL and one exclusive IP per Subscription, that SSL certificate will then apply to all domains in the Subscription, including the one you actually want it for. So it will then work on that domain. That achieves that goal.

But yes, as you say, all the other domains in the Subscription will then use the same Exclusive IP and SSL, but hopefully that's OK? It won't stop them working, and it won't do any harm. They don't use SSL so won't notice a difference, and hopefully the change of IP won't make any difference either?

The inability to move a single domain within a subscription to another Subscription is a pain in the bottom.

http://kb.parallels.com/en/113938

The only solution I know of is to rename/delete the current domain, then recreate it in its own Subscription.
 
Thanks Faris, I really appreciate the reply. It's what I expected - but still surprising. There's a good chance that we'll want SSL certificates for some of the other domains in the subscription/webspace at some point, so I guess we'll just push through the pain now and move the domain. It's too bad this is what Plesk requires!
 
Back
Top