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

SSL woes

michaellunsford

Regular Pleskian
I have an SSL certificate configured on a server. When I visit the :8443 (plesk port) I get the right certificate, but visiting plain old port 443 still presents the self signed.

Here's what I've done so far:
1. had plesk create the CSR. I pasted in the cert and CA.
2. I checked the new cert and clicked the "setup" button, rechecked and clicked the "default" button.
3. under server > ip address, I made the appropriate domain the default domain. I also specified the new certificate under the IP address.

What step did I miss?

PS> this is running on a Virtuozzo VPS, if that matters. When I visit the Virtuozzo port (4643), I get yet another certificate, which looks like the ISP's cert.

EDIT: I have deleted all other certificates from the server and domain control pannels. There is one certificate in plesk -- yet port 443 continues to issue the mystery self-signed certificate.

vhosts/example.com/conf/httpd.include is calling the right cert. Something is apparently overriding this setting.
 
Back
Top