• 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 Certificate not working

J

Jonnerz

Guest
Hey,

I've purchased an SSL certificate and added it into Plesk. I've assiged it to a dedicated IP that the website is hosted on. The problem is that my website is showing a made up certificate with info like 'Organization: SomeOrganization'. I've re-issued and re-added the certificate several times but getting the same error.

When I clicked the "Secure the panel" in the certificate menu, the panel became secured but my site still didn't work. This tells me that it's a problem with plesk/my server rather than the certificate itself. The same problem is happening with the HTTPS of the IP it's assigned to (https://ip.ip.ip.ip).
 
Glad I'm not the only one.

The certificate works fine for the secure panel and for when I use it to secure email but not when used with apache despite it all being setup in plesk correctly. As far as I can tell, the correct certificate is listed in the httpd.include file (of which there are lots) but apache wants to use the default apache certificate instead.
 
I managed to fix it. I changed the IP of the domain/hosting account to something else and then switched it back. It must have refreshed something as it's working fine now.
 
Not for me. I've got 2 IPs, a shared and an exclusive. If I change the ip of the domain with the problem certificate to the shared ip and then back to the exclusive one, the ssl cert problem remains.
 
Interestingly, if I disable SSL support for the domain, it uses the correct SSL certificate but I get the default domain landing page as it's no longer using the shared SSL directory. Re-enabling SSL support goes back to using the wrong SSL cert.

WTF????
 
I'm on 10.3.1 and have the exact same problem -- certificate works to "Secure the Panel" but doesn't work when set as the default SSL for the domain. Has anyone found an answer for this in the past 10 months?
 
I'm on 10.3.1 and have the exact same problem -- certificate works to "Secure the Panel" but doesn't work when set as the default SSL for the domain. Has anyone found an answer for this in the past 10 months?

Me too, I have the same problems over here when I enabling the default domain/site by a certificate that will secure Plesk 10.3.1 also.
 
Last edited by a moderator:
Back
Top