From 43559af0cc75440b0059d43ecc057af24433b598 Mon Sep 17 00:00:00 2001 From: "Thomas R. Koll" Date: Sun, 5 Dec 2021 18:59:39 +0100 Subject: [PATCH] Add a not about creating a backup before starting over I was stupid/tired enough to copy and run that `docker-compose down -v`. Hopefully this little change will prevent others from loosing their data as well. Btw, I did get that page after my disk space was running out. --- data/web/_status.502.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/data/web/_status.502.html b/data/web/_status.502.html index ec6617e4..efbc0e8b 100644 --- a/data/web/_status.502.html +++ b/data/web/_status.502.html @@ -16,8 +16,9 @@ 
docker-compose logs --tail=200 php-fpm-mailcow nginx-mailcow

Make sure your SQL credentials in mailcow.conf (a link to .env) do fit your initialized SQL volume. If you see an access denied, you might have the wrong mailcow.conf:

source mailcow.conf ; docker-compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}
-

In case of a previous failed installation, remove all volumes and start over (NEVER do this with a production system, it will remove ALL data):

- 
docker-compose down -v ; docker-compose up -d
+

In case of a previous failed installation, create a backup of your existing data, followed by removing all volumes and starting over (NEVER do this with a production system, it will remove ALL data):

+ 
BACKUP_LOCATION=/tmp/ ./helper-scripts/backup_and_restore.sh backup all
+ 
docker-compose down --volumes ; docker-compose up -d

Make sure your timezone is correct. Use "America/New_York" for example, do not use spaces. Check here for a list.


Click to learn more about getting support.