Question Anybody facing problems with updating to 18.0.60 or is it safe?

[whu]

Anybody facing problems with updating to 18.0.60 or is it safe?

Just asking before updating:=) Thank you!

 

[ChristophRo]

Already updated all our servers on the 3rd of April (as it finally fixed a Backup Telemetry extension problem for us) and so far no problems with it.

 

[anatol]

We have problems with Plesk Obsidian Version 18.0.60 on Ubuntu right after update.
1. Docker containers with MySQL 8.0.36 do not show logs any more.
2. In Plesk pages there is an error:


3. This error can be fixed by clicking on "Recreate" and recreating the container, the logs will be back, but there will be other warning s in the log like these:


The first one can be temporarily fixed by setting in my.cnf:

[mysqld]
log_error_verbosity = 1
default_authentication_plugin=mysql_native_password

But the second will still remain.

4. It is not possible any more to do mysqldump of DB of Shopware 6 from this container:

 

[carini]

No problem so far. All of our host run under Ubuntu 20.04.6 LTS or Ubuntu 22.04.4 LTS on Azure

 

[LTUser]

No Probs under Ubuntu 20.04.6 LTS and MariaDB 10.6

 

[vargawebkiado]

Anybody facing problems with updating to 18.0.60 or is it safe?

Just asking before updating:=) Thank you!

I have Plesk Obsidian Web Host Edition Version 18.0.60 Ubuntu Linux 22.04.4
After the Plesk update, the websites using Open Journal Systems, Open Monograph Press and Open Preprint Servers became inaccessible. (500) The other (WordPress) websites work without errors.

 

[Hangover2]

@whu I would wait at least for the first or second patch release. As there is no way for downgrading a buggy new release can be a lot of headache. In the past we had to learn that the hard way. When 18.0.60 #1 is released we will start the deployment on our dev servers. I would never install a new version on live servers without testing it on non-critical systems first.