Closed ip6li closed 3 years ago
The problem is you started mailcow with a different mailcow.conf at some point. Running down and up -d will not deinstall mailcow and start a fresh copy. You had a mailcow MySQL volume bootstrapped that didn't match. :)
Environment:
After cloning plain vanilla Mailcow and installing according to documentation I got and endless loop of following messages:
Login to mysql with mysql command using username/password from mailcow.conf failed.
Investigation of that problem revealed, that there is no persistent mysql tablespace.
Workaround: modifying mysql-mailcow volumes from - mysql-vol-1:/var/lib/mysql/:Z to - ./data/mysql-vol-1:/var/lib/mysql/:Z,cached solved problem and mysql tables becomes persistent.
After that workaround and docker-compose down && docker-compose up -d && docker-compose logs -ft a fresh database with credentials from mailcow.conf was created and no more problems occured.