Search results

ON every renew new private keys are generated. I would like to have non changing private keys for TLSA

I would love to see non changing private keys for TLSA, HPKP.

After updating Plesk to 17.5 i get the following Cron Message every day. How can i fix this ?

Is there a chance to disable the mail notification of kav? /etc/cron.daily/kav8update: Loading engine... Current product version: 8.0.1.25 Initializing engine... Using xml-file: /opt/kav/sdk8l3/bin/settings.xml. LICENSE INFO: Key file: kav.key Expiration date: 26/07/2017

Do i need this package? I don't use the WAF or other Atomicorp products.

OS: Debian Jessie Problem: WARNING: The following packages cannot be authenticated! aum Install these packages without verification? [y/N] Please fix this Package.

Thanks @UFHH01

See http://download1.parallels.com/Plesk/PP12/plesk-12.5-for-linux-change-log.html [-] On CentOS 7 x64 servers, after installing MariaDB version 10 or 10.1 the MySQL component was marked as “not installed” in the Plesk Installer. (PPP-18000) So i was confused, if MariaDB 10.1 is supported or not.

Is Plesk 12.5 compatible with Mariadb 10.1? Can i easly upgrade from Mariadb 10 ? Thanks.

Hey. I have the same Problem. And it points to an external Email Service. But i'm using Plesk 12.5

See http://talk.plesk.com/threads/why-plesk-12-5-supports-weak-diffie-hellman.334794/

http://autoinstall.plesk.com/PHP_5.6/ is linked to http://autoinstall.plesk.com/PHP_5.6.12/ instead of http://autoinstall.plesk.com/PHP_5.6.13/

Currently IonCube 4.7.2 is default by Plesks PHP Packages. (plesk-php56-ioncube-loader) For some reasons some software needs 5.xx because its encoded by the ionCube version 9 PHP Encoder. (The Vendor PHP Packages have an actual Ioncube Loader - php5-ioncube-loader)

How do i properly upgrade Ioncube on PHP Plesk 5.6? If i update ioncube_loader_lin_5.6.so it will be updated on every Plesk PHP update. May Plesk will update Ioncube on the next PHP Release ?

Thanks for your answer. I'm using Plesk 12.5 and Debian8. Editing /etc/nginx/conf.d/ssl.conf works fine for me. My "main" Question was why Plesk 12.5 has no "Patch" Out of the Box.

I found an better solution as editing plesk template files. If you add ssl_dhparam /etc/nginx/dhparam.pem; in ssl.conf it also works. Is this unsecure ?

Is there a reason why Plesk 12.5 hasn't patched Logjam? There are several sultions in the Forum, but why is there no "offical" (without editing files) Patch included in Plesk 12.5 ?