| <!DOCTYPE html> |
| <html> |
| <head> |
| <title>Preparing</title> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| </head> |
| <body style='background-color:#fff;color:#333;width: 60%;margin: 0 auto;text-align:left;font-family: Verdana, "Lucida Sans Unicode", sans-serif'> |
| <h1 style="color:#333;font-size:48px">What is happening?</h1> |
| <p style="color:green;font-weight:bold;">Please do not stop the stack while we are initializing the database or do other preparations.</p> |
| <p style="font-size:small"><b>What is happening?</b> - Nginx cannot connect to an upstream server or other services are not ready yet.<br> |
| This is fine if mailcow was just |
| installed or updated and can take a few minutes to complete.<br> |
| Please check the logs or contact support if the error persists.</p> |
| <h2>Quick debugging</h2> |
| <p>Check Nginx and PHP logs:</p> |
| <pre>docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow</pre> |
| <p>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:</p> |
| <pre>source mailcow.conf ; docker compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}</pre> |
| <p>In case of a previous failed installation, create a backup of your existing data, followed by removing all volumes and starting over (<b>NEVER</b> do this with a production system, it will remove <b>ALL</b> data):</p> |
| <pre>BACKUP_LOCATION=/tmp/ ./helper-scripts/backup_and_restore.sh backup all</pre> |
| <pre>docker compose down --volumes ; docker compose up -d</pre> |
| <p>Make sure your timezone is correct. Use "America/New_York" for example, do not use spaces. Check <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones">here</a> for a list.</p> |
| <br>Click to learn more about <a style="color:red;text-decoration:none;" href="https://docs.mailcow.email/#get-support" target="_blank">getting support.</a> |
| </body> |
| </html> |