Error establishing a database connection. Find which half failed.
The server is down, the credentials are wrong, or the disk is full. Those are three jobs. Restarting MySQL is only right for one of them.
Process, login, or the file that names them
MariaDB or MySQL is stopped. The error log says why. A full disk is the first check. A restart on a full volume fails the same way.
Wrong user, wrong host, or a password the panel changed. The daemon is fine. We match the grant to the config file. We do not reset every account.
After a move, wp-config or the panel points at a name that was not imported. The connection works. The schema is missing. That is a restore, not a grant.
Recovery is the last dump, not a repair of an empty file
If the only copy was on this disk, there is nothing to restore. We say that after the first look. A binlog may cover the gap if it was enabled and the disk still has it.
€55 an hour to find which half failed
Minimum 1 hour. Production database down is emergency at €95, subject to availability. The restore itself is included in that time if the dump is on the server. Fetching it from storage you have not given us access to is not.
Site says it cannot connect, and a restart did nothing?
Tell us the exact error and the panel. No database password in the first message.