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

Why doesn't 'disablesslv3' affect the Plesk 8443 interface?

HostaHost

Silver Pleskian
Can someone at Plesk (the company) alter the behavior of Plesk (the software) so that when the disablesslv3 option is set:

http://kb.odin.com/en/123160

that it affects the port 8443 server as well? It seems kind of stupid to have to manually edit the /etc/sw-cp-server/config file. Well it's stupid to have SSLv3 enabled by default anyway, but if someone already took the time to build the functionality that looks for disablesslv3 in the database and then acts on it, it should also update the Plesk 8443 port.
 
This article is for old Plesk 11.5 version. SSLv3 is disabled by default in Plesk 12.5 version.
 
Back
Top