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

Question "This site can’t provide a secure connection" in Chrome and Edge

rcacciato

New Pleskian
Our website generates this error in Chrome and Edge:

This site can’t provide a secure connection​

blue-iceberg.com sent an invalid response.


ERR_SSL_PROTOCOL_ERROR

What's odd is that it's fine in Safari and Firefox. When I run the SSL test in sslshopper.com, I get that it's OK (screenshot attached) but when I run a test on ssllabs.com we get an F (2nd screenshot). I have other sites that fail the OpenSSL Padding Oracle Vulnerability test and get an F but they work fine. I'd like to address this but the critical difference seems to be that this test shows "This site works only in browsers with SNI support." while the sites that are fine don't show that. How do I fix it? I don't see anything that addresses this in Plesk.

Thanks in advance.
 

Attachments

  • Screenshot 2023-11-22 at 12.35.58 PM.png
    Screenshot 2023-11-22 at 12.35.58 PM.png
    230.2 KB · Views: 7
  • Screenshot 2023-11-22 at 12.31.34 PM.png
    Screenshot 2023-11-22 at 12.31.34 PM.png
    182.3 KB · Views: 7
So I've been told that part of the problem is that our versions of Apache and OpenSSL are too old. I have been advised to update them on another discussion list (community.letsencrypt.org) but can't update these in Plesk. The server is running Plesk Onyx Version 17.8.11 Update #94. I thought that an upgrade to Plesk Obsidian would solve this but our hosting company, GoDaddy, is not willing to do this on our server yet. I'm angry because we used to host with Mediatemple which had good tech support but they were acquired by GoDaddy and we were migrated to a new server recently which I believe is the root of all these problems.

My question is: if I update Apache and OpenSSL manually via SSH, will that break Plesk Onyx or will things still be OK?
 
Can we assume that you are also on an unsupported operating system? What's the OS and version?
 
Thanks, AYamshanov. If I update Apache and OpenSSL via SSH, will it "break" Plesk Onyx? I don't think our hosting provider is open to an upgrade... Also will it leave the old versions of PHP in place? Thanks in advance.
 
Unfortunately, I can't guarantee anything just because CentOS6 is not supported, Plesk Onyx is not supported either, I do not know how exactly the server is configured. In this case, my recommendation is to plan a migration to up2date OS and Plesk with Plesk Migrator, to be honest.

If you still want to upgrade the server, I would strongly suggest to create a backup of whole server somewhere externally (not on the same server) and also check that it will be possible to restore it if necessary. Such changes on unsupported servers are always a risk.
 
OK, it's taken me a while to realize this... I'm running a Wordpress site (www.quatt.com) on the same server with a Letsencrypt certificate. The site has a secure connection. So it appears that if the configuration is correct, the SSL connection can be established with the versions of CentOS and OpenSSL I have installed. So there must be some setting that enables a secure connection vs. the settings that prevent a secure connection. Any ideas?
 
Back
Top