Search results

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; =...

i found this Key authorization file did not match "There’s a known bug that affects some users related to the Let’s Encrypt account id. Can you try setting your account email again under Settings (you can update it to the same email address), this will reset the Let’s Encrypt account id...

There are no new certificates they already exist and can not be renewed. Even if I reach the domain via http the same error occurs. Even if I delete the existing certificate and create a new one, the same error occurs.

Plesk 17.8.11 Update #63 Centos 7.6.1810 Lets Engrypt 2.8.2 On a server I get the message from today with several Domains Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/xz9ySowKdL8eOJDAdpbFkldCSjTeyCbS-EKcflSFSJ4. details: Type: urn: ietf: params: acme: error...

Hi, The Plesk docu says: Note: If Plesk does not manage the DNS for the domain, the Let's Encrypt extension can not add the DNS record automatically. In this case, you will see the following message: "Please add a DNS record with the following parameters". Add a DNS record with the specified...

Hi, we transfer many accounts from confixx to plesk. this usually works very well, but a question has arisen that, should there be a solution to save some time. the migrator sets all migrated domains to php7.3-fpm. In order for the site to work for old customers we set the php version of the...

the bug was fixed in the new version 3.6.3-1626. The cloning process works again.

please test this: dbuser only access locally if in the wp-config.php is registered: define ('DB_HOST', 'localhost'); Cloning works if in the wp-config.php is registered: define ('DB_HOST', 'localhost: 3306'); Cloning does not work. Access denied for user 'wordpress_ad'@'::1' (using...

on our servers, all databases are only locally accessible by default. what can be wrong with our configuration if the servers work well for years with the wordpress toolkit and only since the last update anymore? it does not matter if it's centos 6.9 server with mysql 5.6.43 or centos 7 with...

hi, php 7.0 is end of life. change the php version to 7.1 or newer.

We use on all servers a local DB Server. On centos 6.9 Servers Mysql 5.6.x On centos 7 Servers MariadDB 10.1.x

I have found out the solution or the cause of the problem and ask you to take this as a bug and eliminate it as soon as possible. If external access is allowed for a databaseuser then the cloning process starts normally. If only local access is allowed for the database user, the above error...