I want to start this by saying, I feel really dumb that I cannot understand how custom Nginx configuration works and I feel like I have searched the whole internet to try and understand them but I am just not able to comprehend what I am doing wrong. I am aware there is a page dedicated to the configuration of Mailcow behind an Nginx reverse proxy (https://docs.mailcow.email/post_installation/reverse-proxy/r_p-nginx/) but my issue is where do I actually put this configuration? When I customise this configuration to what I believe is my correct details and add it to the Advanced section on the Nginx proxy host for my mail server it goes instantly offline when I push save. I have added it to a .conf file and added it as an additional volume on my Nginx docker container then specified it as a custom location for Mailcow on Nginx but I get the same issue. restarting both Mailcow and Nginx or removing and recomposing the containers still yields the exact same issues of being offline. I am using Mailcow in docker using this guide https://github.com/christianlempa/videos/tree/main/mailcow-tutorial for installing Mailcow. I changed Mailcow HTTP to 85 and HTTPS to 445 and have 80 and 443 ported forward to my Nginx reverse proxy. I have swapped the listening ports of the config below to both 80 and 85 and 443 and 445 for testing but still cannot get it to work. server { listen 80 default_server; listen [::]:80 default_server; server_name mail.mydomain.com autodiscover.mydomain.com autoconfig.mydomain.com; return 301 https://$host$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name mail.mydomain.com autodiscover.mydomain.com autoconfig.mydomain.com; ssl_certificate docker_volumes/mailcow-dockerized/data/assets/ssl/cert.pem; ssl_certificate_key docker_volumes/mailcow-dockerized/data/assets/ssl/key.pem; ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_session_tickets off; # See https://ssl-config.mozilla.org/#server=nginx for the latest ssl settings recommendations # An example config is given below ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5:!SHA1:!kRSA; ssl_prefer_server_ciphers off; location /Microsoft-Server-ActiveSync { proxy_pass http://192.168.50.250:85/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://192.168.50.250:85/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } } Thank you in advance and any help in understanding how custom configurations work would be greatly appreciated!

Rightio, so here is everything I have learned! This is everything you need to configure in the Advanced tab (adjust the IP and port according to your setup for both locations.) Everything else above this from the Mailcow website is already configured elsewhere in Nginx Reverse Proxy so you are doubling up and causing issues if you try to use it. Well done to @"DocFraggle"#1599 for giving me the complete answer without me realising. location /Microsoft-Server-ActiveSync { proxy_pass http://127.0.0.1:8080/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://127.0.0.1:8080/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } Port any other ports you need for mail server 25, 465, 587, 993, 4190, etc to the IP of docker host. make sure you add all 3 hostnames (mail.domain.com, autodiscover.domain.com and autoconfig.domain.com) to the domains names section on your Nginx reverse proxy host as well as on the SSL certificate tab. You will need to download the SSL certificate, copy it to YOUR_MAILCOW_PATH//data/assets/ssl/ and rename the cert and key file to cert.pem and key.pem then restart your container. You will need to copy the new certificate every 3 months to this location manually, I have not figured out a way do get the ACME request to work through proxy. I hope this helps someone! Huge shoutout to @"DocFraggle"#1599 especially for his persistence and patience! If anyone has any ideas how to maybe get the certificate request to work, let me know and we might be able to work it out together.

Please, PLEASE use the "Insert code" button to wrap your config, nobody can read this... What exactly did you configure in your mailcow.conf, especially this part as stated in the overview page (example below): ``` HTTP_BIND=127.0.0.1 HTTP_PORT=8080 HTTPS_BIND=127.0.0.1 HTTPS_PORT=8443 ``` You set the proxy_pass part to an upstream IP address (192.168.50.250), that's why I'm asking. If you used 127.0.0.1 in your mailcow.conf this can't work

Thank you for replying, I really appreciate it! This is what I currently have configured in that section. I have tried with the loopback address and the actual IP in the BIND section but still no good. HTTP_PORT=85 HTTP_BIND= HTTPS_PORT=445 HTTPS_BIND=

@"EverythingBySam"#p15648 Set this in mailcow.conf: ``` HTTP_BIND=127.0.0.1 HTTP_PORT=8080 HTTPS_BIND=127.0.0.1 HTTPS_PORT=8443 ``` ### **_RESTART mailcow afterwards!!!_** ``` docker compose down docker compose up -d ``` And this in your prox_pass lines: ``` location /Microsoft-Server-ActiveSync { proxy_pass http://127.0.0.1:8080/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://127.0.0.1:8080/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } ``` Just like in the docs,

That seems to of worked and did not knock it offline so thank you but I would like Autodiscover to work as well if possible.

Autodiscover should work as well then as long as you set your DNS config according to the docs, and the certificate was enrolled correctly

@"DocFraggle"#p15651 I have a CNAME autodiscover record for autodiscover.domain.com to go to mail.autodiscover.com. I do not have anything configured on my Nginx itself to recognise autodiscover.domain.com When I add those extra lines from the recommend config it goes offline again.

> @"EverythingBySam"#p15652 When I add those extra lines from the recommend config What do you mean? These lines? `server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*;`

@"DocFraggle"#p15653 nah this whole section: server { listen 80 default_server; listen [::]:80 default_server; server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*; return 301 https://$host$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*; ssl_certificate MAILCOW_PATH/data/assets/ssl/cert.pem; ssl_certificate_key MAILCOW_PATH/data/assets/ssl/key.pem; ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_session_tickets off; # See https://ssl-config.mozilla.org/#server=nginx for the latest ssl settings recommendations # An example config is given below ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5:!SHA1:!kRSA; ssl_prefer_server_ciphers off;

Yes, just use the config from here: https://docs.mailcow.email/post_installation/reverse-proxy/r_p-nginx/ And of course replace CHANGE_TO_MAILCOW_HOSTNAME with your mailserver's FQDN

@"DocFraggle"#p15655 I did use that but if I add the top section I put in my previous comment it takes the proxy offline and no longer works.

Nginx Reverse proxy configuration

mailer

I don’t understand correctly. Do I have to log in for Fail2Ban? I can’t log in because the page says 403 Forbidden. Can I just stop the Netfilter container? I also have Fail2Ban in the operating system but that stopped.

esackbauer

mailer I also have Fail2Ban in the operating system

Please don’t do this in the mailcow VM, you are adding error sources. Mailcow has already Netfilter/fail2ban function built in. Remove the fail2ban altogether and leave that job for mailcow itself or your NPM.
In the Netfilter page in your mailcow UI you should see who is blocked. I have a similar setup as you have, I have whitelisted the IP address of my reverse proxy in netfilter.
Try first to publish mailcow without the NPM, directly with SNAT rule, and then check Netfilter settings

mailer

I removed fail2ban completely with apt purge. But it was also stopped beforehand. It didn’t change anything. Still 403 forbidden.
I don’t know how to configure access without NPM, can you describe it in more detail? Do you mean access directly with https://IP in the browser? Sorry I am not really an expert at the moment.

esackbauer

mailer Do you mean access directly with https://IP in the browser?

Yes.

mailer Sorry I am not really an expert at the moment.

Then you should start running mailcow in its basic configuration. You can switch to NPM later also.

mailer

Ok then I understood it correctly and I also tested access via the IP beforehand. There is always the 403 forbidden error and a “Permission denied” entry in the mailcow nginx container. If I want direct access, do I have to change anything in mailcow.conf?

esackbauer

mailer do I have to change anything in mailcow.conf?

No, it should work out of the box unless you fiddled with some settings.
Also important to know is any changes to config files in mailcow directory need docker compose up -d to make them active. Rebooting alone does not apply changes!

mailer

Ok then it’s weird. Yes, I run docker compose down and docker compose up -d every time.
The mailcow.conf is standard except for Let’s Encrypt skip yes and an address for watchtower notification is entered.

esackbauer

If you are logged in in your mailcow VM, what output does curl http://local-IP give? Local-IP being the IP address of your mailcow VM.
Is it just a short error message or does it show the html code of the login page?

mailer

This here:
[root@mail /opt/mailcow-dockerized]# curl http://192.168.1.13 <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html>

And in mailcow nginx container:
`2024/05/13 11:11:15 [error] 20#20: *20 “/web/index.php” is forbidden (13: Permission denied), client: 192.168.1.13, server: urlname, request: “GET / HTTP/1.1”, host: “192.168.1.13”

192.168.1.13 - - [13/May/2024:11:11:15 +0200] “GET / HTTP/1.1” 403 146 “-” “curl/8.5.0”`

esackbauer

Is there another nginx installation running in that mailcow VM itself or in another container?

mailer

No I think not:

[root@mail /opt/mailcow-dockerized]# ps -efwww | grep nginx root 4518 4498 0 10:29 ? 00:00:00 nginx: master process nginx -g daemon off; systemd+ 4633 4518 0 10:29 ? 00:00:00 nginx: worker process systemd+ 4634 4518 0 10:29 ? 00:00:00 nginx: worker process systemd+ 4635 4518 0 10:29 ? 00:00:00 nginx: worker process systemd+ 4636 4518 0 10:29 ? 00:00:00 nginx: worker process systemd+ 4637 4518 0 10:29 ? 00:00:00 nginx: cache manager process
If this were the case, no log entries should arrive in mailcow nginx or?
The only docker containers are in the root context is portainer, watchtower and mailcow.

esackbauer

mailer If this were the case, no log entries should arrive in mailcow nginx or?

correct.
Then I can only assume that your mailcow installation is somehow broken, and I do not know where to search further. Maybe somebody else has an idea, lets wait.

mailer

Thank you for your effort, I had actually already deleted everything and reinstalled it, but maybe I’ll try this again, maybe on a different VM.

EverythingBySam

mailer I have had this error when I was messing around with everything. Make sure your HTTP and HTTPS bind are set to the IP of your docker container or VM with Mailcow not the loopback address (127.0.0.1) and the correct HTTP and HTTPS port that you have exposed for Mailcow access.

Make sure NPM is also set to use the IP of the Docker machine or VM you have Mailcow installed on, not the loop address as well as the correct HTTP or HTTPS port you set it to.

Finally, make sure the advanced configure is set to use the actual IP address of the VM or Docket machine not the loop back address.

Like previously stated, don’t forget to download and copy the SSL certificate into correct location in your Mailcow folder.

All this has to match!

mailer

Ok, I’m a little confused now. In the history of this article the address 127.0.0.1 is used everywhere for example as bind address or in the advanced tab from NPM, but I shouldn’t use this now but the IP of the VM, right?
And the certificate that the NPM generated has to be imported now and cannot only be done at the end when access is working, right?

esackbauer

mailer In the history of this article the address 127.0.0.1 is used everywhere for example as bind address

No, the default in mailcow.conf is NOT 127.0.0.1. That can only be used if NPM runs on the same VM, for obious reason as 127.0.0.1 ist called LOCALHOST.
Seems you have a lot to learn on networking…

So in your case, if you have mailcow running in a separate VM than your NPM/reverse proxy, leave mailcow bindings as thei are, and simply point the NPM to the default ports on the IP of the mailcow VM.
Certificate in mailcow is a self signed when it starts up the first time. So you are able to access mailcow.

mailer

Ok, I have now entered the IP address in “bind” and inserted the advanced tab in NPM and also adjusted the IP address and port there. It remains 403 forbidden. Even if I want to call mailcow locally with the IP address.
I haven’t transferred the certificate yet, I’ll do that now but I don’t think that will change anything.

esackbauer

mailer I have now entered the IP address in “bind”

leave them empty, that is the default.
Don’t forget to do docker compose up -d afterwards.

The nginx 403 error could also be wrong rights on the docker volumes or installation directory, maybe there something was messed up? Are you trying to start mailcow as non-root?

mailer but I don’t think that will change anything.

correct. Won’t change the error message.

mailer

Ok, I’m one step further now. I looked at everything again and realized that I had hardened my VM a long time ago. I changed the umask. I have now set this back to 0022 as described in the documentation. I’m sorry I didn’t notice it sooner.
I downloaded mailcow again from Github and recreated the containers.
I haven’t entered a bind in mailcow.conf and nothing in the NPM under advanced tab at the moment.
If I now want to call mailcow via NPM or https://IP, I see a “Preparing” page with the following text:

`What is happening?
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 or other services are not ready yet.
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.
Quick debugging
Check Nginx and PHP logs:

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, 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.`

With this command:
docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow
I see the following log:

`[root@mail /opt/mailcow-dockerized]# docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow
WARN[0000] /opt/mailcow-dockerized/docker-compose.yml: `version` is obsolete 
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: using the "epoll" event method
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: nginx/1.25.5
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: built by gcc 13.2.1 20231014 (Alpine 13.2.1_git20231014) 
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: OS: Linux 6.8.0-31-generic
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start worker processes
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start worker process 20
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start worker process 21
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start worker process 22
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start worker process 23
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start cache manager process 24
nginx-mailcow-1  | 2024/05/13 22:01:36 [notice] 1#1: start cache loader process 25
nginx-mailcow-1  | 2024/05/13 22:02:29 [error] 20#20: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.1, server: MYURL, request: "GET / HTTP/1.1", upstream: "fastcgi://172.22.1.7:9002", host: "MYURL"
nginx-mailcow-1  | 2024/05/13 22:02:29 [error] 20#20: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.1, server: MYURL, request: "GET / HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::a]:9002", host: "MYURL"
nginx-mailcow-1  | 172.19.0.1 - - [13/May/2024:22:02:29 +0200] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0"
nginx-mailcow-1  | 2024/05/13 22:02:36 [notice] 25#25: http file cache: /tmp 0.000M, bsize: 4096
nginx-mailcow-1  | 2024/05/13 22:02:36 [notice] 1#1: signal 17 (SIGCHLD) received from 25
nginx-mailcow-1  | 2024/05/13 22:02:36 [notice] 1#1: cache loader process 25 exited with code 0
nginx-mailcow-1  | 2024/05/13 22:02:36 [notice] 1#1: signal 29 (SIGIO) received
nginx-mailcow-1  | 2024/05/13 22:05:30 [error] 22#22: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.1, server: MYURL, request: "GET / HTTP/1.1", upstream: "fastcgi://172.22.1.7:9002", host: "MYURL"
nginx-mailcow-1  | 2024/05/13 22:05:30 [error] 22#22: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.1, server: MYURL, request: "GET / HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::a]:9002", host: "MYURL"
nginx-mailcow-1  | 172.19.0.1 - - [13/May/2024:22:05:30 +0200] "GET / HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0"
nginx-mailcow-1  | 2024/05/13 22:05:42 [error] 21#21: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.73, server: MYURL, request: "GET / HTTP/2.0", upstream: "fastcgi://172.22.1.7:9002", host: "192.168.1.13"
nginx-mailcow-1  | 2024/05/13 22:05:42 [error] 21#21: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.73, server: MYURL, request: "GET / HTTP/2.0", upstream: "fastcgi://[fd4d:6169:6c63:6f77::a]:9002", host: "192.168.1.13"
nginx-mailcow-1  | 192.168.1.73 - - [13/May/2024:22:05:42 +0200] "GET / HTTP/2.0" 502 2015 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0"
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  | 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  | 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  | 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  | 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  | 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  | 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  | 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...
`

Now what could this be?
I left the mailcow.conf completely standard except for my URL

EverythingBySam

mailer Not sure if this will help you but I had the same issue but clearing out the entire folder helps

docker compose down -v

docker compose up -d

DocFraggle

EverythingBySam but clearing out the entire folder

FYI, that’s not clearing a folder, that’s just restarting the whole mailcow installation 😉

« Previous Page