• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

SSL for www.domainname.com

P

Peach@

Guest
I'm starting a new thread. My original tread was here:
http://forum.swsoft.com/showthread.php?s=&threadid=39638

I now have correct Private Key and Certificate files. The certificate was issued for www.domainname.com. I have a default domain, domainname.com. I still can't get it to work :(

I'm still confused about a few things, though.

1) Do I install it under Domains > domainname.com > Certificates or under Server > Certificates?

I created a new certificate in both areas using the same certficate and private key. It seems like that the only way I can assign a certificate to an IP address is if I installed it under Server (I only have 1 IP). I rather use my new certificate everywhere, so this is what I did:

I've made the new certificate in the Server area to be the default, pressed the Setup button, in Server > IP Addresses >, I selected the new certificate, stopped/started httpd.

Unfortunately, the old default certificate still shows up.

2) Do I have to create a subdomain, www.domainname.com? The WWW check box is selected for domainname.com. Is this not enough for a certificate for www.domainname.com to work? If I'm making this domain the default certificate, it doesn't seem to matter, but I'm not sure.

Also, I don't mean to go off topic too much, but I did try creating www.domainname.com once earlier today. When I created it, though, www.domainname.com was no longer accessible via a web browser. So I deleted the subdomain and rechecked "WWW" in the domainname.com, but I couldn't access www.domainame.com anymore. I restarted my browser, httpd, but it was no longer there. It took about an hour, and all the sudden it started working. I don't understand it. So I'm afraid to try it again :(

Thanks!

----------------
UPDATE - one more question.

My hosting company is now telling me that I have to purchase a second IP for my certificate to work. Is it true? I'm deleting the default certificate, so my new certificate is the only one under this IP. I'm even more confused....
 
You will need to install the ssl cert on the 2nd IP. Your main IP would be for shared hosts. You need an exclusive IP.
 
Well, I was finally able to set up a SSL certificate with only 1 IP and multiple domains. This is the only SSL for this IP, so I felt like it should work. I had to force it by following the directions in this thread: http://forum.swsoft.com/showthread....&threadid=35761
but it's working now.

I ended up creating a subdomain www.domainname.com as I decided to redirect all https://domainname.com to https://www.domainname.com by inserting a RedirectPermanent directive in vhost_ssl.conf file.
 
Back
Top