• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue "Export Dump"-function (Obsidian 18.0.52) doesn't work with MySQL 5.1

JoeJoe

New Pleskian
Server operating system version
Windows Server 2012
Plesk version and microupdate number
Obsidian 18.0.52
After install "Obsidian 18.0.52"-updating, database's "Export Dump"-function doesn't work. It seems there is a compatibility issue with MySQL 5.1 database...

screen3.jpg
 
I inadvertently had automatic updates turned on, and our Plesk got updated. Now, I can't back up our databases and the scheduled backups also fail. Is there a way to back down to a version that supports MySQL 5.6? This is a production box, so I need to be careful.
 
You cannot downgrade. Instead, why not upgrade the ancient MySQL to a modern version?
This is a production server, running other software. We are in the process of standing up a new box, but at the moment, we are seemingly unable to backup our databases from Plesk. Which means, we will have to backup each schema manually from WorkBench. Ugh.
 
Back
Top