Search results

have you already updated to 18.0.21 Update 3?

Does anyone know what the "SelectBestBuild function" is about? if the two servers in my example would be different but that's not the case. both servers are exactly the same. same os had same extensions same configuration.

yes, the update settings are the same everywhere what I have found so far: on a machine that has automatically updated (autoinstallerlog) on a machine that has not updated automatically (autoinstallerlog) what is "The SelectBestBuild function" ?

some of the servers have automatically updated within the first two days after the appearance of 18.0.21 and the other part not, but after the login only shows an "An upgrade to Plesk Obsidian 18.0.21 is available." if every month new upgrades appear, they always have to be triggered manually...

where at Plesk Obsidian should this attitude be? Under Tools - Update Settings is nothing.

I have noticed that on some systems the update from 18.0.20 to 18.0.21 was automatically installed and on some system this is not automatically installed. the update settings are the same everywhere. Where can I look for what the problem could be?

could someone please check if this manual for centos 6/7 is correct? yum install perl-Razor-Agent pyzor pyzor --homedir /etc/mail/spamassassin discover mkdir /etc/mail/spamassassin/.razor sudo razor-admin -home=/etc/mail/spamassassin/.razor -register sudo razor-admin...

maybe you have upgraded mariadb 10.1 to 10.2 ? Troubleshooting Row Size Too Large Errors with InnoDB ALTER TABLE clients ROW_FORMAT=DYNAMIC; should eliminate the warning. always make a backup before

thanks ales for the info this is of course great if the developer of a server software implements a rule without first checking exactly whether the clients fully implement this rule. then we'll wait and see whether either the clients make corrections or courier changes.

Hi Igor, thank you for your message. but that is not a pure outlook problem. there are customers who use thunderbird or macmail and also have this message. This only happens with isolated emails. For example, a customer receives an email a day from an email distributor and suddenly after the...

I can report that we have updated more than 100 servers so far and there is no problem.

thanks for the information. no risk no fun :) I have made the update from 10.1.41 to 10.1.43 on a previously affected machine and mariadb has started without errors after the update.

MariaDB has removed all affected versions from their repository. MariaDB has fixed the issue in the following unpublished versions: 10.1.43 [ 23703 ] 10.2.29 [ 23911 ] 10.3.20 [ 23909 ] 10.4.10 [ 23907 ] I do not know when these will be published

thanks for the information. if several have reported the problem then the problem can certainly be solved by plesk. we just have to be patient.

please give feedback here what Plesk support has said.

we have also customers reporting that since the update to obsidian they're receiving the following message: we use:

Is this really a fact that you can not "upgrade" a migrated server (confixx) to Plesk Obsidian? The Mysqlpasswords are criticized because they were apparently migrated engrypted. To reset the Mysqlpassword with hundreds of accounts is a huge effort. what happens if you do the upgrade despite...

Yes, after update to 18.0.20 it is fixed.

>> Could you check the output of the following command? output is ssl-cipher-server-order: 1 when click sync now ssl it sets ssl_prefer_server_ciphers off >> Anyway, this is a bug in SSL It. I hope it will be fixed someday. i hope so.

After Upgrade to Obsidian and activate SSL It! - TLS versions and encodings of Mozilla SSL-Labs shows only Grade B. Plesk Onyx - nginx.conf ssl_ciphers EECDH+AESGCM+AES128........ ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_dhparam /usr/local/psa/etc/dhkey.pem; =...