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

Issue Problems with SSL certificate

lynxcoder

New Pleskian
Hello all,
I have a reasonable, but not extensive server background, but am fairly new to Plesk! We have a new Centos7 server, and through the Plesk front end we have installed a Lets Encrypt free SSL onto the master domain abc.com and a secondary domain abc.co.uk which is redirected to the .com site through a .htaccess 301 redirect.

The certificate appears to have installed correctly, and we can access the site fine on all the machines we can try, but general traffic through the site has dropped by 50% since moving to the new server, and a small number of people have contacted us saying that they are getting certificate errors. From lots of Googling (I have VERY limited experience of SSL certificates) it appears to be a well known and reported issue to do with a Root Certificate expiry last September - which ties in with what we are seeing when we do a Qualys SSL report on the domain. There are two paths, one has three entries and is trusted, one has four entries and is 'Not Trusted'

Screenshot 2022-02-23 at 18.48.53.png

Various forum and web posts seem to explain the problem, but nobody seems to describe how to solve it in Plesk. It may involve delving into the command line, but being new to Plesk and on a live server, I am loathe to wade too much for fear of disrupting the Plesk install. Can any one offer me any suggestions on how we solve this or pointers to where to look? I have had a search through this forum, but nothing seems to come up. I am assuming either entry 4 needs to be removed or updated somehow?

I am somewhat tearing my hair out now (and dont have that much left!!) so any help would be very gratefully received.

Thanks
Richard
 
Back
Top