Login Issues with Mailcow Panel

adminroan24

Hello,

I’m experiencing an issue logging into the Mailcow panel. Here are some details:

Authentication: I’ve ensured I’m using the correct username and password, but after entering them, a message appears saying “Please wait,” and the login does not proceed.
Update: This issue arose after a recent Mailcow update.
Browser: I’ve tried logging in from different browsers and have cleared the cache and cookies, but it hasn’t resolved the issue.
Server Access: I have access to the server where Mailcow is running, and all containers seem to be up and running.
Logs: I checked the server logs and didn’t find any clear errors indicating the cause.
Firewall and Network: I’ve also checked if any firewall or network settings might be blocking access, and everything seems fine.
Has anyone encountered a similar issue or has any suggestions on what might be causing this? I would appreciate any advice or suggestions.

Thank you and best regards,
Roland

DocFraggle

Did you try to restart mailcow?

docker compose down
docker compose up -d

adminroan24

Hello,

I followed your suggestion and ran docker compose down and then docker compose up -d. Unfortunately, this didn’t resolve the issue. I also tried updating the application again, and now both the admin panel and the webmail interface are inaccessible, showing a 502 error on the web page.

Here’s what else I have tried:

I checked the server logs but didn’t find any clear errors indicating the cause.
All containers appear to be up and running, including Redis.
I verified that no firewall or network settings are blocking access.
Email functionality still works, as I can send and receive emails through Thunderbird.
I’m at a loss as to what to do next. Any further guidance would be greatly appreciated.

Thank you,
Roland

DocFraggle

Which version did you upgrade from? Do you use a reverse proxy? Are you running other Docker containers besides Mailcow on this host?

adminroan24

Thank you for your response.

I don’t recall the exact version I upgraded from, but my current version is “mailcow/sogo:1.123”. Additionally, I’m using a reverse proxy, and there are no other Docker containers besides Mailcow running on this host.

I tried another update, but now both the admin and webmail interfaces display a “502 Bad Gateway” error. Interestingly, I can still send and receive emails via Thunderbird.

The web interfaces can be accessed at:

Mail Panel
Admin Panel
Do you have any other suggestions on what I might try?

Thank you and best regards,
Roland

DocFraggle

adminroan24 I would suggest checking your reverse proxy config first. I bet that Mailcow itself is working fine, but your reverse proxy can’t connect.

You can check if the Web UI is working by accessing it with curl from your Mailcow host system. First, check which port the Mailcow UI is running on:

cd /opt/mailcow-dockerized     # (if that's your mailcow location)
grep HTTPS_PORT mailcow.conf

Then connect via curl using this port (for example 1234):

curl -kv https://127.0.0.1:1234/

If you get a proper output Mailcow is working fine and you have to have a look at your reverse proxy config.

adminroan24

As suggested, I checked the reverse proxy configuration:

I first ensured Mailcow itself was working fine by accessing its web interface from the host server using curl.
The port was verified using grep HTTPS_PORT mailcow.conf, showing port 443.
Connecting to the web interface using curl -kv https://127.0.0.1:443 resulted in a 502 Bad Gateway error.
This suggests that the issue may be related to the reverse proxy itself or another aspect of the configuration.
I then restarted the Nginx service, but the problem persists.
Do you have additional suggestions regarding the reverse proxy configuration or any other actions I could take?

Thanks for your help!

DocFraggle

Hmm, port 443, ok… why do you use a reverse proxy in the first place? Which port is your reverse proxy listening on? I’m asking because you normally would run Mailcow on a different port than 443 (i.e. 1234), your reverse proxy on 443 and have it connect to your Mailcow instance on port 1234)

Please run

netstat -tulpen

and paste the output. Also, please paste the output of your reverse proxy config

adminroan24

I ran the netstat -tulpen Active Internet connections Proto Recv-Q Send-Q Local Address tcp 0 0 127.0.0.1:19991 tcp 0 0 0.0.0.0:25 tcp 0 0 127.0.0.1:13306 tcp 0 0 0.0.0.0:443 tcp 0 0 0.0.0.0:4190 tcp 0 0 0.0.0.0:993 tcp 0 0 0.0.0.0:995 tcp 0 0 127.0.0.1:7654 tcp 0 0 127.0.0.1:18983 tcp 0 0 0.0.0.0:587 tcp 0 0 0.0.0.0:110 tcp 0 0 0.0.0.0:143 tcp 0 0 0.0.0.0:9999 tcp 0 0 0.0.0.0:80 tcp 0 0 0.0.0.0:465 tcp 0 0 127.0.0.53:53 tcp6 0 0 :::25 tcp6 0 0 :::4190 tcp6 0 0 :::993 tcp6 0 0 :::995 tcp6 0 0 :::587 tcp6 0 0 :::110 tcp6 0 0 :::143 tcp6 0 0 :::9999 tcp6 0 0 :::8080 tcp6 0 0 :::465 udp 0 0 127.0.0.53:53 command and here is the output:
(only servers)
Foreign Address State User Inode PID/Program name
0.0.0.0:* LISTEN 0 223189829 3725844/docker-prox
0.0.0.0:* LISTEN 0 223188631 3725431/docker-prox
0.0.0.0:* LISTEN 0 223183718 3725273/docker-prox
0.0.0.0:* LISTEN 0 225381486 3850917/docker-prox
0.0.0.0:* LISTEN 0 223187825 3725883/docker-prox
0.0.0.0:* LISTEN 0 223187840 3725923/docker-prox
0.0.0.0:* LISTEN 0 223188752 3725902/docker-prox
0.0.0.0:* LISTEN 0 223184553 3724960/docker-prox
0.0.0.0:* LISTEN 0 224910907 3844213/docker-prox
0.0.0.0:* LISTEN 0 223187613 3725390/docker-prox
0.0.0.0:* LISTEN 0 223187852 3725967/docker-prox
0.0.0.0:* LISTEN 0 223192657 3725945/docker-prox
0.0.0.0:* LISTEN 0 37120 1249/sshd: /usr/sbi
0.0.0.0:* LISTEN 0 225377660 3850931/docker-prox
0.0.0.0:* LISTEN 0 223186680 3725411/docker-prox
0.0.0.0:* LISTEN 101 28474 1145/systemd-resolv
:::* LISTEN 0 223188634 3725438/docker-prox
:::* LISTEN 0 223186803 3725889/docker-prox
:::* LISTEN 0 223189846 3725931/docker-prox
:::* LISTEN 0 223188755 3725909/docker-prox
:::* LISTEN 0 223193366 3725397/docker-prox
:::* LISTEN 0 223187855 3725975/docker-prox
:::* LISTEN 0 223194427 3725953/docker-prox
:::* LISTEN 0 37122 1249/sshd: /usr/sbi
:::* LISTEN 0 215953647 3009618/apache2
:::* LISTEN 0 223188610 3725419/docker-prox
0.0.0.0:* 101 28473 1145/systemd-resolv

sysadmin@mailgo:~/mailcow-dockerized$ sudo docker exec -it mailcowdockerized-nginx-mailcow-1 sh
/ # cd /etc/nginx
/etc/nginx # cat nginx.conf

user nginx;
worker_processes auto;

error_log /var/log/nginx/error.log notice;
pid /var/run/nginx.pid;

events {
worker_connections 1024;
}

http {
include /etc/nginx/mime.types;
default_type application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                  '$status $body_bytes_sent "$http_referer" '
                  '"$http_user_agent" "$http_x_forwarded_for"';

access_log  /var/log/nginx/access.log  main;

sendfile        on;
#tcp_nopush     on;

keepalive_timeout  65;

#gzip  on;

include /etc/nginx/conf.d/*.conf;

}
/etc/nginx #

================
/etc/nginx # cat /etc/nginx/conf.d/mailcow_admin.conf
server {
listen 80;
listen [::]:80;
server_name mail.roan24.pl;
return 301 https://$server_name$request_uri;
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name mail.roan24.pl;

ssl_certificate /etc/ssl/mail/cert.pem;
ssl_certificate_key /etc/ssl/mail/key.pem;
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m;
ssl_session_tickets off;

ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;

location / {
    proxy_pass http://php-fpm-mailcow:9000/;
    proxy_set_header Host $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 100M;
}

}
/etc/nginx # cat /etc/nginx/conf.d/site.conf
proxy_cache_path /tmp levels=1:2 keys_zone=sogo:10m inactive=24h max_size=1g;
server_names_hash_max_size 512;
server_names_hash_bucket_size 128;

map $http_x_forwarded_proto $client_req_scheme {
default $scheme;
https https;
}

include /etc/nginx/conf.d/sites.active;
/etc/nginx # cat /etc/nginx/conf.d/redirect.conf
server {
root /web;
listen 80 default_server;
listen [::]:80 default_server;
include /etc/nginx/conf.d/server_name.active;
if ( $request_uri ~* “%0A|%0D” ) { return 403; }
location ^~ /.well-known/acme-challenge/ {
allow all;
default_type “text/plain”;
}
location / {
return 301 https://$host$uri$is_args$args;
}
}
/etc/nginx #

It seems the reverse proxy is listening on port 443 and other services like Mailcow are functioning fine. What do you suggest next?

We checked the reverse proxy configuration files:

mailcow_admin.conf: This redirects traffic from port 80 to port 443. It also forwards HTTPS traffic to the Mailcow admin interface running on php-fpm-mailcow:9000.
site.conf: Defines a cache path and includes configurations from sites.active. It also maps client request schemes.
redirect.conf: Defines a server that listens on port 80 and redirects HTTP traffic to HTTPS URLs. It also permits requests to .well-known/acme-challenge/.
Do let us know what you think or if there’s something else we should check!

DocFraggle

No, it doesn’t look like you are using a reverse proxy at all 😉

Run

docker compose logs --tail=1 -f nginx-mailcow

then try to connect to your UI and have a look at the logs

adminroan24

We checked the reverse proxy configuration files:

DocFraggle

Ah you edited your post… please use the “Insert code” button to format your pasted config, no one can read that properly

From what I can see you are running both mailcow and nginx on port 80/443, that can’t work

adminroan24

sysadmin@mailgo:~/mailcow-dockerized$ sudo docker compose logs –tail=1 -f nginx-mailcow
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:17 +0200] “HEAD /settings.php HTTP/1.1” 304 0 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.4 - - [30/Apr/2024:10:22:24 +0200] “GET / HTTP/1.1” 200 15 “-” “check_http/v (nagios-plugins 2.4.5)”
mailcowdockerized-nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [30/Apr/2024:10:22:29 +0200] “GET /forwardinghosts.php?host=178.251.229.9 HTTP/1.1” 200 19 “-” “curl/7.74.0”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:38 [error] 21#21: *2524 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET / HTTP/2.0”, upstream: “http://172.22.1.9:9000/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:38 [warn] 21#21: *2524 upstream server temporarily disabled while reading response header from upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET / HTTP/2.0”, upstream: “http://172.22.1.9:9000/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:38 [error] 21#21: *2524 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET / HTTP/2.0”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:38 [warn] 21#21: *2524 upstream server temporarily disabled while reading response header from upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET / HTTP/2.0”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 37.47.156.83 - - [30/Apr/2024:10:22:38 +0200] “GET / HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:39 [error] 21#21: *2524 no live upstreams while connecting to upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET /favicon.ico HTTP/2.0”, upstream: “http://php-fpm-mailcow/favicon.ico”, host: “mail.roan24.pl”, referrer: “https://mail.roan24.pl/”
mailcowdockerized-nginx-mailcow-1 | 37.47.156.83 - - [30/Apr/2024:10:22:39 +0200] “GET /favicon.ico HTTP/2.0” 502 559 “https://mail.roan24.pl/” “Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:40 [error] 21#21: *2524 no live upstreams while connecting to upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET / HTTP/2.0”, upstream: “http://php-fpm-mailcow/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 37.47.156.83 - - [30/Apr/2024:10:22:40 +0200] “GET / HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:40 [error] 21#21: *2524 no live upstreams while connecting to upstream, client: 37.47.156.83, server: mail.roan24.pl, request: “GET /favicon.ico HTTP/2.0”, upstream: “http://php-fpm-mailcow/favicon.ico”, host: “mail.roan24.pl”, referrer: “https://mail.roan24.pl/”
mailcowdockerized-nginx-mailcow-1 | 37.47.156.83 - - [30/Apr/2024:10:22:40 +0200] “GET /favicon.ico HTTP/2.0” 502 559 “https://mail.roan24.pl/” “Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:47 +0200] “GET /footer.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.4 - - [30/Apr/2024:10:22:47 +0200] “GET / HTTP/1.1” 200 15 “-” “check_http/v (nagios-plugins 2.4.5)”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:47 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:47 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:47 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:47 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 188.125.224.90 - - [30/Apr/2024:10:22:48 +0200] “GET /SOGo/ HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:48 [error] 21#21: *2538 no live upstreams while connecting to upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://php-fpm-mailcow/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:49 [error] 21#21: *2538 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://172.22.1.9:9000/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:49 [warn] 21#21: *2538 upstream server temporarily disabled while reading response header from upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://172.22.1.9:9000/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:49 [error] 21#21: *2538 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:49 [warn] 21#21: *2538 upstream server temporarily disabled while reading response header from upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 188.125.224.90 - - [30/Apr/2024:10:22:49 +0200] “GET /SOGo/ HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:50 [error] 21#21: *2538 no live upstreams while connecting to upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://php-fpm-mailcow/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 188.125.224.90 - - [30/Apr/2024:10:22:50 +0200] “GET /SOGo/ HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:22:51 [error] 21#21: *2538 no live upstreams while connecting to upstream, client: 188.125.224.90, server: mail.roan24.pl, request: “GET /SOGo/ HTTP/2.0”, upstream: “http://php-fpm-mailcow/SOGo/”, host: “mail.roan24.pl”
mailcowdockerized-nginx-mailcow-1 | 188.125.224.90 - - [30/Apr/2024:10:22:51 +0200] “GET /SOGo/ HTTP/2.0” 502 559 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:22:58 +0200] “HEAD /settings.php HTTP/1.1” 304 0 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.4 - - [30/Apr/2024:10:23:07 +0200] “GET / HTTP/1.1” 200 15 “-” “check_http/v (nagios-plugins 2.4.5)”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:08 +0200] “HEAD /forwardinghosts.php HTTP/1.1” 200 0 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | fd4d:6169:6c63:6f77::5 - - [30/Apr/2024:10:23:08 +0200] “GET /forwardinghosts.php HTTP/1.1” 200 27 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 167.94.145.98 - - [30/Apr/2024:10:23:09 +0200] “GET / HTTP/1.1” 301 169 “-” “-” “-”
mailcowdockerized-nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [30/Apr/2024:10:23:13 +0200] “GET /forwardinghosts.php?host=91.241.74.125 HTTP/1.1” 200 19 “-” “curl/7.74.0”
mailcowdockerized-nginx-mailcow-1 | 167.94.145.98 - - [30/Apr/2024:10:23:15 +0200] “GET / HTTP/1.1” 301 169 “-” “Mozilla/5.0 (compatible; CensysInspect/1.1; +https://about.censys.io/)” “-”
mailcowdockerized-nginx-mailcow-1 | 167.94.145.98 - - [30/Apr/2024:10:23:17 +0200] “PRI * HTTP/2.0” 400 157 “-” “-” “-”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:19 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:19 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:19 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:19 +0200] “GET /bcc.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 172.22.1.2 - - [30/Apr/2024:10:23:19 +0200] “POST /pushover.php HTTP/1.1” 200 5 “-” “rspamd-3.7.5”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:23:21 [error] 21#21: *2564 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 167.94.145.98, server: mail.roan24.pl, request: “GET / HTTP/1.1”, upstream: “http://172.22.1.9:9000/”, host: “79.137.70.16”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:23:21 [warn] 21#21: *2564 upstream server temporarily disabled while reading response header from upstream, client: 167.94.145.98, server: mail.roan24.pl, request: “GET / HTTP/1.1”, upstream: “http://172.22.1.9:9000/”, host: “79.137.70.16”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:23:21 [error] 21#21: *2564 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 167.94.145.98, server: mail.roan24.pl, request: “GET / HTTP/1.1”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/”, host: “79.137.70.16”
mailcowdockerized-nginx-mailcow-1 | 2024/04/30 10:23:21 [warn] 21#21: *2564 upstream server temporarily disabled while reading response header from upstream, client: 167.94.145.98, server: mail.roan24.pl, request: “GET / HTTP/1.1”, upstream: “http://[fd4d:6169:6c63:6f77::a]:9000/”, host: “79.137.70.16”
mailcowdockerized-nginx-mailcow-1 | 167.94.145.98 - - [30/Apr/2024:10:23:21 +0200] “GET / HTTP/1.1” 502 157 “-” “Mozilla/5.0 (compatible; CensysInspect/1.1; +https://about.censys.io/)” “-”
mailcowdockerized-nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [30/Apr/2024:10:23:23 +0200] “GET /forwardinghosts.php?host=193.203.222.6 HTTP/1.1” 200 19 “-” “curl/7.74.0”
mailcowdockerized-nginx-mailcow-1 | fd4d:6169:6c63:6f77::11 - - [30/Apr/2024:10:23:25 +0200] “GET /forwardinghosts.php?host=195.78.67.47 HTTP/1.1” 200 19 “-” “curl/7.74.0”

DocFraggle

Is your php-fpm-mailcow container really up and healthy? Check it’s logs

adminroan24

I modified the Docker Compose configuration to resolve the port conflict by using ports 1234 and 1235 for Nginx.

sysadmin@mailgo:~/mailcow-dockerized$ sudo docker compose logs –tail=50 -f php-fpm-mailcow
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:38:53 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:38:53 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:38:57 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:38:59 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:38:59 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:38:59 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:38:59 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:38:59] WARNING: [pool system-worker] child 154 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: query rodmost@rodmost.pl as username from mailbox”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:38:59] WARNING: [pool system-worker] child 154 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: mailbox found: rodmost@rodmost.pl”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:38:59] WARNING: [pool system-worker] child 154 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: goto array count on loop #1 is 0”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:38:59] WARNING: [pool system-worker] child 154 said into stderr: “NOTICE: PHP message: NOTIFY: pushover pipe: processing pushover message for rcpt rodmost@rodmost.pl”
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:38:59 +0200 “POST /pushover.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:00 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:01 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:07 +0200 “HEAD /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:07 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:09 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:15 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:15 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:15 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:15 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:15] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: query biuro@osto.pl as username from mailbox”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:15] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: mailbox found: biuro@osto.pl”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:15] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: goto array count on loop #1 is 0”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:15] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: NOTIFY: pushover pipe: processing pushover message for rcpt biuro@osto.pl”
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:15 +0200 “POST /pushover.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:22 +0200 “HEAD /settings.php” 304
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:22 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:22 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:27 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:27 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:27 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:27 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:27] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: query ostroleka@kdf-podatki.pl as username from mailbox”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:27] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: mailbox found: ostroleka@kdf-podatki.pl”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:27] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: goto array count on loop #1 is 0”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:27] WARNING: [pool system-worker] child 153 said into stderr: “NOTICE: PHP message: NOTIFY: pushover pipe: processing pushover message for rcpt ostroleka@kdf-podatki.pl”
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:27 +0200 “POST /pushover.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:27 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:30 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:39:41] WARNING: [pool system-worker] child 165 said into stderr: “NOTICE: PHP message: FOOTER: checking for domain tartakmanex.pl, user biuro@tartakmanex.pl and address biuro@tartakmanex.pl”
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:41 +0200 “GET /footer.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:39:41 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:42 +0200 “HEAD /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:39:42 +0200 “GET /forwardinghosts.php” 200
^Ccanceled
sysadmin@mailgo:~/mailcow-dockerized$

===============

sysadmin@mailgo:~/mailcow-dockerized$ sudo docker compose restart nginx-mailcow php-fpm-mailcow
[+] Restarting 2/2
✔ Container mailcowdockerized-nginx-mailcow-1 Started 2.7s
✔ Container mailcowdockerized-php-fpm-mailcow-1 Started 2.5s
sysadmin@mailgo:~/mailcow-dockerized$

502 Bad Gateway
nginx/1.25.5

===============

502 Bad Gateway
nginx/1.25.5

sysadmin@mailgo:~/mailcow-dockerized$ sudo docker compose logs –tail=50 -f php-fpm-mailcow
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:27] NOTICE: Finishing …
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:27] NOTICE: exiting, bye-bye!
mailcowdockerized-php-fpm-mailcow-1 | Uptime: 347 Threads: 27 Questions: 6289 Slow queries: 0 Opens: 318 Open tables: 309 Queries per second avg: 18.123
mailcowdockerized-php-fpm-mailcow-1 | MySQL @ 65509e1f672241edef7c97c91f97c57aa2795fbfac25ca13bc62e215ae39faf7
mailcowdockerized-php-fpm-mailcow-1 | SQL upgrade iteration #1
mailcowdockerized-php-fpm-mailcow-1 | MySQL is up-to-date - debug output:
mailcowdockerized-php-fpm-mailcow-1 | { “type”: “success”, “msg”: “mysql_upgrade: already upgraded”, “text”: “This installation of MariaDB is already upgraded to 10.5.24-MariaDB.\nThere is no need to run mysql_upgrade again for 10.5.24-MariaDB.\nYou can use –force if you still want to run mysql_upgrade\n” }
mailcowdockerized-php-fpm-mailcow-1 | We are master, preparing…
mailcowdockerized-php-fpm-mailcow-1 | Running DB init…
mailcowdockerized-php-fpm-mailcow-1 | Fixed _sogo_static_view
mailcowdockerized-php-fpm-mailcow-1 | Cleaned up memcached
mailcowdockerized-php-fpm-mailcow-1 | Rebuilding domain map in Redis…
mailcowdockerized-php-fpm-mailcow-1 | find: /web/templates/cache/*: No such file or directory
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:32] NOTICE: fpm is running, pid 1
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:32] NOTICE: ready to handle connections
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:33] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: FOOTER: checking for domain tartakmanex.pl, user biuro@tartakmanex.pl and address biuro@tartakmanex.pl”
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:33 +0200 “GET /footer.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:33 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:33 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:33 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:33 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:40:36 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:36 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:36 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:40:36 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:36 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:38 +0200 “GET /index.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:40 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:40 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:40 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:40:40 +0200 “POST /pipe.php” 505
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:40:40] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: QUARANTINE: Message too large: 10636 b exceeds 0 b”
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:40:45 +0200 “HEAD /settings.php” 304
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:40:49 +0200 “HEAD /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:40:49 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:00 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:02 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:08 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:41:08 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:08 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:08 +0200 “GET /bcc.php” 200
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:41:08] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: query a.savera@vostok.pl as username from mailbox”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:41:08] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: mailbox found: a.savera@vostok.pl”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:41:08] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: RCPT RESOVLER: http pipe: goto array count on loop #1 is 0”
mailcowdockerized-php-fpm-mailcow-1 | [30-Apr-2024 10:41:08] WARNING: [pool system-worker] child 137 said into stderr: “NOTICE: PHP message: NOTIFY: pushover pipe: processing pushover message for rcpt a.savera@vostok.pl”
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:41:08 +0200 “POST /pushover.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:27 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | 172.22.1.8 - 30/Apr/2024:10:41:27 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:27 +0200 “GET /forwardinghosts.php” 200
mailcowdockerized-php-fpm-mailcow-1 | fd4d:6169:6c63:6f77::c - 30/Apr/2024:10:41:35 +0200 “HEAD /settings.php” 304

DocFraggle

So if 1235 now is your SSL port, what’s the curl output now?