The same happened to me.
I restored a user backup from a hestiacp 1.8.11 with mariadb 10.6.18 to a newly installed hestiacp 1.8.12 with mariadb 10.11.6 and all the DBs were empty after the user restore
You have the same issue, MariaDB 10.6.18 has the change applied but MariaDB 10.11.6 doesn’t so the mysql dumps are not compatible. You can use the MariaDB repo instead of the one included in Ubuntu or Debian but I suppose you are using Debian 12 (because of the MariaDB version installed).
If you installed Hestia on Debian 12, check if you already have this repo /etc/apt/sources.list.d/mariadb.list
And will look like this:
#deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/debian bookworm main
If that is the case, edit the repo file, remove the comment #, save it, apt update, apt full-upgrade and once done you should be able to restore the users (including the DBs).
1 Like
Yes, is Debian 12 and the mariadb.list line is commented.
I will follow your tips.
Thanks!
1 Like
I think this issue happens because WordPress isn’t detecting the restored database correctly. You can try the following steps to fix it:
Check wp-config.php – Ensure it has the correct database name, user, and password. If needed, update it with the correct details.
Manually verify the database – Log into MySQL and run:
SHOW TABLES;
If tables are missing, try re-importing the backup.
Update the site URL – Sometimes, the URL needs to be fixed after migration. Run:
UPDATE wp_options SET option_value = ‘http://your-new-domain.com’ WHERE option_name IN (‘siteurl’, ‘home’);
Check for database corruption – Run:
CHECK TABLE wp_options, wp_users;
If corruption is found, try:
REPAIR TABLE wp_options, wp_users;
Also, I would like to share if the database is corrupt and won’t repair, try Stellar Repair for MySQL. It can restore broken tables and recover lost data without affecting the site.