Akeeba Backup for Joomla!

Thursday, 28 November 2024 11:16 CST

Hi there,

used Akeeba before to move my backup to a domain I use to develop the new website, and it all worked fine. Used the same procedure: done a backup from the test site and tried to restore it on the production site. But I'm getting a timeout error. Below the report from Kickstart.

I've used the following data - taken from PHPMyAdmin to connect to the DB:

Database server host name: 89.46.XXX.XX

User: SqlXXXX (like in Utente)

PW: I've used a password that I've generated from the Aruba control panel

Database name: SqlXXXX_1

Prefix: the one generated by Kickstart

The database doesn't have any table. I cleaned that up.

That's what I see in PHPMyAdmin (with hidden addresses)

Server: 62.149.XXX.XX via TCP/IP
Tipo di server: MySQL
Versione del server: 5.0.96-community-log - MySQL Community Edition (GPL)
Versione protocollo: 10
Utente: [email protected]
Codifica caratteri del server: cp1252 West European (latin1)

Tried MySQL as database type, nothing changed.

Can you please put me on the right way?

Best,

Giovanni

Friday, 29 November 2024 00:11 CST

nicholas

The one thing that jumps to me is that you've set up server 89.46.XXX.XX but PHPMyAdmin reports server 62.149.XXX.XX. You should really ask your host what the connection information is.

Moreover, I see that the database server version is way too old (5.0.96). MySQL 5.0 has been End of Life since January 9th, 2012. This database server version is dead for just under 13 years. Even if you get the connection information right, PHP 8.1 won't be able to connect to this ancient database server version. Even if by some miracle (i.e. someone applied a precarious and inadvisable patch) it does, the restoration will ultimately fail because Joomla! 5 requires MySQL 8.0 or later.

You should probably ask your host why they are using, not to put too fine a point on it, the rotting corpse of a long-dead MySQL server version in production instead of a current LTS release of MySQL (8.0 or 8.4). If they refuse to upgrade their server, it's time to move to a different host which doesn't force its customers to use server software that's 13 years out of date, and riddled with security vulnerabilities.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 29 November 2024 04:52 CST

[email protected]

Many thanks, you were right. That was a problem with the obsolete version of MySQL.

All is running fine now!

G

Friday, 29 November 2024 05:46 CST

nicholas

You're welcome! These issues are easy for us developers to spot, but understandably unlikely for most users to catch. I am glad I could help you :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support