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

Question Update OpenSSL on CentOS 6.4 (due to ERR_SSL_PROTOCOL_ERROR message)

IAR

New Pleskian
Hi,

I'm experiencing some issues with websites not loading and showing the following error message on Chrome desktop browser:

This site can’t provide a secure connection​

www.my-blabla-domain.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

From my own research this is due to a very recent update on Chrome version 117. It's clashing with a bug that is present on old versions of OpenSSL.
The websites load fine on other browsers.

Because of this situation, I'm planning to update OpenSSL on the webserver.

These are my server specs:
  • CentOS 6.4 (Final)‬
  • Plesk Onyx Version 17.8.11 Update #94 (July 11, 2023)

What is the best approach for updating OpenSSL?
And from your experience what can go wrong? I would like to anticipate any issues with Let's Encrypt plugin since that's what is used to issue the certificates.

Thanks for your help!
 
Back
Top