Facebook
Twitter-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations. -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
Question Anybody facing problems with updating to 18.0.60 or is it safe?
- Thread starter whu
- Start date
ChristophRo
Regular Pleskian
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.
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:
4. It is not possible any more to do mysqldump of DB of Shopware 6 from this container:
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:
But the second will still remain.
4. It is not possible any more to do mysqldump of DB of Shopware 6 from this container:
Attachments
vargawebkiado
New Pleskian
Hangover2
Regular Pleskian
@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.
