"🐄 - we are on our way. 502"

Krispy

I have attempted to setup mailcow on multiple operating systems multiple times, however I have only been able to get it to work once (that installation failed once I tried to setup redirecting all http requests to https, and I was unable to recover it).

The issue that I always have is the one in the title, I simply always get the same page with the same error:

"🐄 - we are on our way.

502
Please do not stop the stack, while we are initializing the database or do other preparations.

What is happening? - Nginx cannot connect to an upstream server.
This is fine, if mailcow was just installed or updated and can take a few minutes to complete.
Please check the logs or contact support, if the error persists.

docker-compose logs –tail=200 php-fpm-mailcow

Need support?"

I have tried to run the command listed which gives me this output:

root@harold:/opt/mailcow-dockerized# docker-compose logs --tail=200 php-fpm-mailcow Attaching to mailcowdockerized_php-fpm-mailcow_1 php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Waiting for SQL... php-fpm-mailcow_1 | Uptime: 1 Threads: 8 Questions: 3 Slow queries: 0 Opens: 16 Flush tables: 1 Open tables: 10 Queries per second avg: 3.000 php-fpm-mailcow_1 | MySQL @ 9a58b226978d17d44d37ddd9954b0b2903f4d5569b9a31098621fabd0d22925c php-fpm-mailcow_1 | SQL upgrade iteration #1 php-fpm-mailcow_1 | MySQL applied an upgrade, debug output: php-fpm-mailcow_1 | {"msg":"mysql_upgrade: upgrade was applied","text":"Phase 1/7: Checking and upgrading mysql database\nProcessing databases\nmysql\nmysql.column_stats OK\nmysql.columns_priv OK\nmysql.db OK\nmysql.event OK\nmysql.func OK\nmysql.global_priv OK\nmysql.gtid_slave_pos OK\nmysql.help_category OK\nmysql.help_keyword OK\nmysql.help_relation OK\nmysql.help_topic OK\nmysql.index_stats OK\nmysql.innodb_index_stats OK\nmysql.innodb_table_stats OK\nmysql.plugin OK\nmysql.proc OK\nmysql.procs_priv OK\nmysql.proxies_priv OK\nmysql.roles_mapping OK\nmysql.servers OK\nmysql.table_stats OK\nmysql.tables_priv OK\nmysql.time_zone OK\nmysql.time_zone_leap_second OK\nmysql.time_zone_name OK\nmysql.time_zone_transition OK\nmysql.time_zone_transition_type OK\nmysql.transaction_registry OK\nPhase 2/7: Installing used storage engines... Skipped\nPhase 3/7: Fixing views\nmysql.user OK\nPhase 4/7: Running 'mysql_fix_privilege_tables'\nPhase 5/7: Fixing table and database names\nPhase 6/7: Checking and upgrading tables\nProcessing databases\ninformation_schema\nmailcow\nperformance_schema\nPhase 7/7: Running 'FLUSH PRIVILEGES'\nOK\n","type":"warning"} php-fpm-mailcow_1 | Uptime: 2 Threads: 8 Questions: 7 Slow queries: 0 Opens: 16 Flush tables: 1 Open tables: 10 Queries per second avg: 3.500 php-fpm-mailcow_1 | SQL upgrade iteration #2 php-fpm-mailcow_1 | MySQL is up-to-date - debug output: php-fpm-mailcow_1 | {"msg":"mysql_upgrade: already upgraded","text":"This installation of MariaDB is already upgraded to 10.4.17-MariaDB, use --force if you still need to run mysql_upgrade\n","type":"success"} php-fpm-mailcow_1 | Restarting Postfix php-fpm-mailcow_1 | command completed successfully php-fpm-mailcow_1 | Sleeping 5 seconds... root@harold:/opt/mailcow-dockerized#

I have also looked up some possible sollutions on these forums, I found this article https://community.mailcow.email/d/213-502-please-do-not-stop-the-stack-while however that has not changed anything.

I have also tried to avoid my dns and simply connect to the website using the servers ip address however that still results in the same issue, might there be anything I am doing wrong? Is there some simple fix I can use (this has been causing a headache for about 2 days now :/).

Thanks in advance,
Kris.

ValdikSS

I assume there may be a bug related to DNS domain. Could you check if there’s search option listed in /etc/resolv.conf on your server?

Krispy

yes! there is a “Search” option listed in /ect/resolv.conf , the file contains this:
nameserver 127.0.0.53 options edns0 search home telenet.be
what should I change the search to?

ValdikSS

Krispy Try to comment it, restart docker after that. I’m not familiar with Docker, especially if it gets DNS domain from /etc/resolv.conf, but I hope that should help.

Krispy

when you say “restart docker” do you mean do restard the containers or to restart the service, as in instead of docker-compose down -v; docker-compose up -d I should do systemctl restart docker.service?

ValdikSS

docker-compose down
docker-compose up -d

Krispy

ValdikSS this did not fix anything 🙁