I ran the ./update.sh script about two days ago because I had an outdated version of Mailcow. But after the update, which went through normally, Mailcow started displaying an infinite loading screen.
I started doing some basic debugging as best I could and started looking at the logs of all the containers.
watchdog shows this in a loop:
so I started checking the SOGO container, because it shows some errors, but the only thing in the SOGO logs is this:
I guessed that sogo was trying to connect to the mysql database and get some scheme from it, so I started checking the Mysql container and found these two errors:
mysql container shows these two errors continuously in loop.
I checked the passwords and logins in the mailcow.conf file and everything was correct.
So I tried asking chatGPT how I could fix it and he told me to use some upgrade command to install the latest version of MariaDB, which stopped me from seeing these two errors in mysql logs, but sogo still didn’t work and displayed the same logs as before, that it was waiting for a scheme update.
I decided that asking chatGPT for help was a terrible idea, to put it mildly, and I reverted those changes, so now I’m getting the same two errors in the mysql logs again, haha. But digging deeper, I found one anomaly.
in the file /data/web/inc/init_db.inc.php I found this variable:
$db_version = “07102025_1015”;
but searching in the mysql database for the actual scheme version I found this:
I don’t know what to do next, as there’s clearly a completely different scheme version in the database and in this .php file that i found.
I’m a beginner when it comes to servers and have a home server with about 13 mailboxes for hobby purposes. So I decided to ask somewhere where people know more about mailcow than me, as I’d rather not risk doing anything myself.
