mailcow-dockerized/data/web/_status.502.html

<!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://mailcow.github.io/mailcow-dockerized-docs/#get-support" target="_blank">getting support.</a>
  </body>
</html>
[Nginx] Custom 502 2019-09-24 06:53:13 +02:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
[Web] Changes to 502 status page 2019-09-24 07:06:33 +02:00			`<title>Preparing</title>`
[Nginx] Custom 502 2019-09-24 06:53:13 +02:00			`<meta name="viewport" content="width=device-width, initial-scale=1.0">`
			`</head>`
[Web] Improve Nginx default error page 2021-05-12 21:38:21 +02:00			`<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`
[Web] Changes to 502 status page 2019-09-24 07:06:33 +02:00			`installed or updated and can take a few minutes to complete.<br>`
[Web] Improve Nginx default error page 2021-05-12 21:38:21 +02:00			`Please check the logs or contact support if the error persists.</p>`
			`<h2>Quick debugging</h2>`
			`<p>Check Nginx and PHP logs:</p>`
Use built in compose 2022-12-16 14:57:13 +02:00			`<pre>docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow</pre>`
[Web] Improve Nginx default error page 2021-05-12 21:38:21 +02:00			`<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>`
Use built in compose 2022-12-16 14:57:13 +02:00			`<pre>source mailcow.conf ; docker compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}</pre>`
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. 2021-12-05 19:59:39 +02:00			`<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>`
Use built in compose 2022-12-16 14:57:13 +02:00			`<pre>docker compose down --volumes ; docker compose up -d</pre>`
[Web] Improve Nginx default error page 2021-05-12 21:38:21 +02:00			`<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://mailcow.github.io/mailcow-dockerized-docs/#get-support" target="_blank">getting support.</a>`
[Nginx] Custom 502 2019-09-24 06:53:13 +02:00			`</body>`
			`</html>`